[lm-sensors] move to new website - status?

[lm-sensors] move to new website - status?

[Rudolf Marek]

Hi all,

What is missing to complete the move to trac? Here is the list what I think needs to be fixed:

1) picture issue?
2) "extended formating" wiki feature is not enabled?
3) port the newdrivers/supported table (implies 2 is enabled)
4) port ticket system
5) switch to svn completely

Anything else?

Thanks
Regards
Rudolf

[lm-sensors] move to new website - status?

[Axel Thimm]

On Fri, Jan 20, 2006 at 11:02:53PM +0100, Rudolf Marek wrote:
> What is missing to complete the move to trac? Here is the list what
> I think needs to be fixed:
> 
> 1) picture issue?
> 2) "extended formating" wiki feature is not enabled?
> 3) port the newdrivers/supported table (implies 2 is enabled)
> 4) port ticket system
> 5) switch to svn completely
> 
> Anything else?

The flipping picture issue in trac seems to be a known issue, but
there is still no upstream fix for it. I'd place that further back in
the queue to give upstream a chance to fix it. OR to allow
experimenting with switching from cgi to mod_python serving, which
might fix the issue (since the bug seems to be in trac's cgi methods).

The switch to svn can be done as soon as everyone with current CVS
write access is comfortable with the test svn repo. The repo can be
remigrated from current CVS within short time, so as soon as there is
agreement, give us the go, and we'll set it up for good.

That's the first item I'd like to see done.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060121/ef7a0483/attachment.bin

[lm-sensors] move to new website - status?

[Rudolf Marek]

Hello,


> The flipping picture issue in trac seems to be a known issue, but
> there is still no upstream fix for it. I'd place that further back in
> the queue to give upstream a chance to fix it. OR to allow
> experimenting with switching from cgi to mod_python serving, which
> might fix the issue (since the bug seems to be in trac's cgi methods).

OK

> The switch to svn can be done as soon as everyone with current CVS
> write access is comfortable with the test svn repo. The repo can be
> remigrated from current CVS within short time, so as soon as there is
> agreement, give us the go, and we'll set it up for good.

OK
> That's the first item I'd like to see done.
OK I will send you my pub key and will start to learn how to live with svn :)

Well we need to convert the newdrivers/supported thats the last thing left (from web perspecitive)

Quoting Jean some time ago:
> Quoting Michael Renzmann a few days ago:
> 
> << Some of the remaining pages, most notably the "supported devices" and
> "new drivers" ones, use tables with cells that span more than one row
> and/or column. This type of table can be better rendered when support
> for "restructured text" is enabled, see:
> http://lm-sensors.org/trac/wiki/WikiRestructuredText - any chance we get
> this on the lm_sensors Trac installation? >>
> 
Please can you do that?

Phil, what about the ticket system conversion as Jean mentioned it?

Thanks
Regards
Rudolf

[lm-sensors] move to new website - status?

[Philip Edelbrock]

On Jan 21, 2006, at 1:47 AM, Rudolf Marek wrote:

>
> Phil, what about the ticket system conversion as Jean mentioned it?

Hi Rudolf and Jean, thanks for following up.

I've processed the old tickets and put them into the new trac schema  
for Axel.  I don't have write access to the trac database (which is  
fine), so I've done two things:

- I've uploaded a sql script which contains the old tickets into my  
home directory on the server.  It is called "old-tickets-trac.sql".   
It requires that there be a new component called 'legacy' so that we  
can keep these tickets apart from the new ones. (sql: insert into  
component values ('legacy','somebody','import from legacy ticket  
system'); )

- I've taken a copy of the current trac database (trac.db) and  
already added the new component and imported the tickets.  Again this  
db (still named trac.db) is in my home directory if you want to use  
that, Axel.

A couple notes:

- The SQL comes from a Perl script, so if it looks/works aweful, I  
can tweak the script as needed and run another dump.  I haven't see  
what this actually looks like in Trac yet, so if needed, we can try  
it again.

- The dates are the same on all the tickets.  If it is important to  
keep the dates, I can work on it some more.  Trac's schema uses an  
integer to store dates instead of datetime/timestamp types.

- For some reason tickets 125 and 126 didn't import.  We can just  
copy and paste those in.  Not bad considering there are over 2,000+  
tickets!


Phil

[lm-sensors] move to new website - status?

[Jean Delvare]

Hi Axel,

> On Fri, Jan 20, 2006 at 11:02:53PM +0100, Rudolf Marek wrote:
> > What is missing to complete the move to trac? Here is the list what
> > I think needs to be fixed:
> > 
> > 1) picture issue?
> > 2) "extended formating" wiki feature is not enabled?
> > 3) port the newdrivers/supported table (implies 2 is enabled)
> > 4) port ticket system
> > 5) switch to svn completely
> > 
> > Anything else?
> 
> The flipping picture issue in trac seems to be a known issue, but
> there is still no upstream fix for it. I'd place that further back in
> the queue to give upstream a chance to fix it. OR to allow
> experimenting with switching from cgi to mod_python serving, which
> might fix the issue (since the bug seems to be in trac's cgi methods).

Any news about this? I don't see the picture flipping anymore myself,
so it seems to be fixed. Anyone still having the problem?

Axel, did you enable the extended formating as Rudolf asked? We need it.

> The switch to svn can be done as soon as everyone with current CVS
> write access is comfortable with the test svn repo. The repo can be
> remigrated from current CVS within short time, so as soon as there is
> agreement, give us the go, and we'll set it up for good.

Do you have enough ssh key by now? We can't switch until you have at
least mine, Rudolf's and Mark Hoffman's. Others can send their key
later, after we have collectively agreed to grant them write access, of
course.

BTW, will it be possible to have different permissions for the i2c and
lm_sensors2 repositories? I'd like to grant more people developer
access to lm_sensors2, but write access to the i2c repository needs to
be restricted as changes to it are supposed to be very rare now.

Now that lm_sensors 2.10.0 has been released, I think it is a really
good time to switch to SVN, if nobody objects. Phil, could you switch
the i2c and lm_sensors2 CVS repositories to read-only? So we are
certain that changes are not lost. Note that the website repository
should be kept writable so that we can at least announce the website
change.

About the tickets, I think Phil was done with porting the old tickets
to Trac, is it true? Anything left to do on this front?

Thanks,
-- 
Jean Delvare

[lm-sensors] move to new website - status?

[Axel Thimm]

Hi,

On Sun, Feb 19, 2006 at 01:47:07PM +0100, Jean Delvare wrote:
> > On Fri, Jan 20, 2006 at 11:02:53PM +0100, Rudolf Marek wrote:
> > > What is missing to complete the move to trac? Here is the list what
> > > I think needs to be fixed:
> > > 
> > > 1) picture issue?
> > > 2) "extended formating" wiki feature is not enabled?
> > > 3) port the newdrivers/supported table (implies 2 is enabled)
> > > 4) port ticket system
> > > 5) switch to svn completely
> > > 
> > > Anything else?
> > 
> > The flipping picture issue in trac seems to be a known issue, but
> > there is still no upstream fix for it. I'd place that further back in
> > the queue to give upstream a chance to fix it. OR to allow
> > experimenting with switching from cgi to mod_python serving, which
> > might fix the issue (since the bug seems to be in trac's cgi methods).
> 
> Any news about this? I don't see the picture flipping anymore myself,
> so it seems to be fixed. Anyone still having the problem?

There was no feedback on the list, but the latest trac release fixed
this apparently.

> Axel, did you enable the extended formating as Rudolf asked? We need it.

Not yet, I found out I have to build some bits to support this like
python-docutils.

> > The switch to svn can be done as soon as everyone with current CVS
> > write access is comfortable with the test svn repo. The repo can be
> > remigrated from current CVS within short time, so as soon as there is
> > agreement, give us the go, and we'll set it up for good.
> 
> Do you have enough ssh key by now? We can't switch until you have at
> least mine, Rudolf's and Mark Hoffman's.

No, only you sent a key and I already had Phil's.

> Others can send their key later, after we have collectively agreed
> to grant them write access, of course.
> 
> BTW, will it be possible to have different permissions for the i2c and
> lm_sensors2 repositories? I'd like to grant more people developer
> access to lm_sensors2, but write access to the i2c repository needs to
> be restricted as changes to it are supposed to be very rare now.

Not through ssh access. In this case the developer only sees a
database there is no fine grained per file/directory access. If you
want to go that way there are two possibilities:

o Have separate repos for lm_sensors and i2c. That would not be nice,
  as it would effectively mean separate trac installs, too.

o don't use ssh access, but http & dav

I think if there will be ACLs then we'd need to go with http &
dav. For the users/developers this might be even nicer, as the URL is
the same as the ones for the anonymous access.

In that case, authentication wouldn't happen anymore with ssh keys,
but via http/https methods.

I'd recommend to make sure the repo layout is compatible with the idea
of different ACLs for i2c and lm_sensors (e.g. top level dirs are
lm_sensors/i2c and trunk/branch/tag comes beneath), and start with ssh
key authentication for now, which is already set up. We can later
switch to a different authentication schemes to allow for ACLs.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060219/7ecda881/attachment.bin

[lm-sensors] move to new website - status?

[Axel Thimm]

On Sun, Feb 19, 2006 at 02:28:52PM +0100, Axel Thimm wrote:
> > BTW, will it be possible to have different permissions for the i2c and
> > lm_sensors2 repositories? I'd like to grant more people developer
> > access to lm_sensors2, but write access to the i2c repository needs to
> > be restricted as changes to it are supposed to be very rare now.
> 
> Not through ssh access. In this case the developer only sees a
> database there is no fine grained per file/directory access. If you
> want to go that way there are two possibilities:
> 
> o Have separate repos for lm_sensors and i2c. That would not be nice,
>   as it would effectively mean separate trac installs, too.
> 
> o don't use ssh access, but http & dav
> 
> I think if there will be ACLs then we'd need to go with http &
> dav. For the users/developers this might be even nicer, as the URL is
> the same as the ones for the anonymous access.
> 
> In that case, authentication wouldn't happen anymore with ssh keys,
> but via http/https methods.
> 
> I'd recommend to make sure the repo layout is compatible with the idea
> of different ACLs for i2c and lm_sensors (e.g. top level dirs are
> lm_sensors/i2c and trunk/branch/tag comes beneath), and start with ssh
> key authentication for now, which is already set up. We can later
> switch to a different authentication schemes to allow for ACLs.

I forgot to mention that the http access method has the nice
sideeffect that you can share the same authentication with trac, that
also uses http authentication.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060219/472222ee/attachment.bin

[lm-sensors] move to new website - status?

[Philip Edelbrock]

On Feb 19, 2006, at 5:28 AM, Axel Thimm wrote:

> Hi,
>
> On Sun, Feb 19, 2006 at 01:47:07PM +0100, Jean Delvare wrote:
>>> On Fri, Jan 20, 2006 at 11:02:53PM +0100, Rudolf Marek wrote:
>>>> What is missing to complete the move to trac? Here is the list what
>>>> I think needs to be fixed:
>>>>
>>>> 1) picture issue?
>>>> 2) "extended formating" wiki feature is not enabled?
>>>> 3) port the newdrivers/supported table (implies 2 is enabled)
>>>> 4) port ticket system

The tickets have been moved over.  Notice that the old status is in  
the subject.  Change or remove that if you change the status of a  
ticket.  Or, if that's too much of a hassle, I can try to strip those  
out for non-closed tickets.

All tickets are 'minor' to start with.  Change the priority as  
necessary.

'Components' were carried over from the old ticket system.  Let me  
know if you want more.

I don't know what milestones would make sense, or if they are even  
needed.

I'll put some versions that make sense in that pulldown.

Unless there are any show stoppers, please dive in and categorize,  
prioritize, and hopefully fix some bugs!

>> [...]
>> Any news about this? I don't see the picture flipping anymore myself,
>> so it seems to be fixed. Anyone still having the problem?
>
> There was no feedback on the list, but the latest trac release fixed
> this apparently.
>

Yes, it seems to be fixed for me.


Phil