Menu
▾
▴
lcd4linux-devel
|
From: Maxime P. <max...@bu...> - 2004-12-28 11:43:27
|
Lcd4linux developpers, Michael, As you can probably guess from the preceding mail by Xavier, I'm posting here to present a solution to your Wiki and Bugtracking needs. The solution i'm bringing to you today is based on a wonderful tool called Trac[1]. It's a web-based software project management system. Trac relies on Python, Sqlite and Subversion. In your situation (and considering the mail entitled 'lcd4linux wiki' =66rom Michael, sent 2004-12-12 on this list), I see a couple of advantages. First of all, Trac is a Wiki. It will allow you to build a full website quickly, and it will provide a excellent documentation support (one of your requirements was that each contributor could maintain it's plugin documentation. This will be possible). Next, Trac provides a Roadmap system. It list incoming milestones with descriptions. Tickets (I'll tell more on them later) targeted for a specific milestone are aggregated, and the ratio between active and resolved tickets is displayed as a milestone progress bar. A Timeline let you know of almost everything new on the project : commits, page edits, tickets creations/closings, etc. Finally, the tickets. Trac tickets are the bugtracking system. By specifying some key information in the tickets (milestone, severity, priority, ...), Trac is able to build sorted tickets list (by milestone, by priority, ...). I'm hosting a demo[2] Trac environment. You can login as trac admin using demo/demo. Feel free to test all the features. You can also check an active Trac environment, with milestones and tickets filled on the Zwe[3] webpage. The only drawback I see in this migration is that Trac is based on Subversion. I can host the related Subversion repository without any problem, but if you are currently hosted by SF, it meens that you are using CVS. But considering the migration would be interesting. Subversion[4] is a more powerfull tool than CVS, and the import from CVS is possible. I don't have a very good upload speed (128kbits/s), but I have a very good connection uptime. I can also provide other kind of hostings if you need : DNS/Mail/SSH/Web/MySQL/additional svn repos/..., just ask and it= can be done in the next 5 minutes :P Here it is. Enjoy- Regards, - Sam [1] Trac: http://projects.edgewall.com/trac [2] Demo: https://ssl.bulix.org/projects/demo [3] Zwe : https://ssl.bulix.org/projects/zwe [4] Svn : http://subversion.tigris.org For information, the box that provides the hosting is my personnal server, running for bulix.org. It runs Debian 3.1. You can take a look at the hardware at https://ssl.bulix.org/phpsysinfo. As this box host my $HOME via NFS, I just can't let it fall. --=20 / Maxime Petazzoni - <max...@bu...> - bulix.org | | Zwe (zwe.bulix.org) - TracTux (https://tractux.bulix.org) | | Gpg Id: 0x83E6AE0D - Jabber: sa...@ja... ________________/ |
|
From: Xavier V. <xav...@fr...> - 2004-12-28 13:05:42
|
Le mardi 28 d=E9cembre 2004 =E0 12:43 +0100, Maxime Petazzoni a =E9crit : > In your situation (and considering the mail entitled 'lcd4linux wiki' > from Michael, sent 2004-12-12 on this list), I see a couple of > advantages. > First of all, Trac is a Wiki. It will allow you to build a full > website quickly, and it will provide a excellent documentation support > (one of your requirements was that each contributor could maintain it's > plugin documentation. This will be possible). One question, is it possible for guests to modify pages, or must one be authentified ? It could be usefull to let some pages within full access. Moreover, are there some ACL implemented ? I mean is it possible to create a "documentation" group which could only modify pages related to doc ? (maybe not useful for us, but worth knowing) > Next, Trac provides a Roadmap system. It list incoming milestones with > descriptions. Tickets (I'll tell more on them later) targeted for a > specific milestone are aggregated, and the ratio between active and > resolved tickets is displayed as a milestone progress bar. > A Timeline let you know of almost everything new on the project : > commits, page edits, tickets creations/closings, etc. > Finally, the tickets. Trac tickets are the bugtracking system. By > specifying some key information in the tickets (milestone, severity, > priority, ...), Trac is able to build sorted tickets list (by > milestone, by priority, ...). I saw it for zwe, it's excellent :p > The only drawback I see in this migration is that Trac is based on > Subversion. I can host the related Subversion repository without any > problem, but if you are currently hosted by SF, it meens that you are > using CVS. But considering the migration would be > interesting. Subversion[4] is a more powerfull tool than CVS, and the > import from CVS is possible. On the other hand, SF CVS servers are not known to be reliable and I won't be bothered to switch to somethinkg else ... Bye ! --=20 Xavier VELLO <xav...@fr...> |
|
From: Maxime P. <max...@bu...> - 2004-12-28 13:30:46
|
Hi Xavier, > One question, is it possible for guests to modify pages, or must one > be authentified ? It could be usefull to let some pages within full > access. > Moreover, are there some ACL implemented ? I mean is it possible to > create a "documentation" group which could only modify pages related > to doc ? (maybe not useful for us, but worth knowing) Trac currently implements basic permission management. You can restrict the wiki edition (and a lot of others features) to authenticated users (or a specific user) only. I suggest you read the Trac permissions documentation[1]. In the future, Trac will support per-page ACL. > On the other hand, SF CVS servers are not known to be reliable and I > won't be bothered to switch to somethinkg else ... Hehe, you're right. But don't forget that Svn is pretty different from CVS, and there will be some re-education to be done for all developpers. You can read more and start learning using the Subversion Book[2]. - Sam [1] http://projects.edgewall.com/trac/wiki/TracPermissions [2] http://svnbook.red-bean.com/ -- / Maxime Petazzoni - <max...@bu...> - bulix.org | | Zwe (zwe.bulix.org) - TracTux (https://tractux.bulix.org) | | Gpg Id: 0x83E6AE0D - Jabber: sa...@ja... ________________/ |
|
From: Michael R. <re...@eu...> - 2004-12-29 01:52:16
|
Hi there, >>On the other hand, SF CVS servers are not known to be reliable and I >>won't be bothered to switch to somethinkg else ... > > Hehe, you're right. But don't forget that Svn is pretty different from > CVS, and there will be some re-education to be done for all > developpers. You can read more and start learning using the Subversion > Book[2]. You are right, SVN is probably a lot better that CVS. I already thought about switching to SVN. But my/our primary goal is to get 0.10 out to the public. Changing source code management infrastructure at this point is Not The Right Thing (tm). Let's stay with SF CVS for the time being, let 0.10 become stable, and then switch to SVN. bye, Michael -- Michael Reinelt <re...@eu...> http://members.eunet.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
|
From: Xavier V. <xav...@fr...> - 2004-12-28 13:42:13
|
> > On the other hand, SF CVS servers are not known to be reliable and I > > won't be bothered to switch to somethinkg else ... > Hehe, you're right. But don't forget that Svn is pretty different from > CVS, and there will be some re-education to be done for all > developpers. You can read more and start learning using the Subversion > Book[2]. As for myself, I just had two little scripts to update and commit with commands taken from some SF doc and never really cared about how it worked. So if migrating to subversion is just changing these scripts, it won't be difficult :p -- Xavier VELLO <xav...@fr...> |
|
From: Xavier V. <xav...@fr...> - 2004-12-28 13:57:13
|
I found a tool called cvs2svn ( http://cvs2svn.tigris.org/cvs2svn.html ) which can help us to migrate the CVS content to a new subversion repository. -- Xavier VELLO <xav...@fr...> |
|
From: Michael R. <re...@eu...> - 2004-12-29 02:09:49
|
Hi List, Maxime, Thanks for your mail and your explanations. This sounds great (although I didn't find the time to have a closer look, for a simple reason: Got Spellforce: Shadow of Phoenix as a cristmas present :-( As I wrote in another mail, we *have to* release 0.10 aka CVS. The code is stable for half a year now, the only reason for not releasing it is the lack of documentation (the internals of lcd4linux changed a lot, and therefore the current docs are completely out of date). And we have to implement some of the features 0.9.11 had and 0.10 lacks (GPIO support, virtual screens/scrolling and so on...) For we didn't even start writing/changing docs for 0.10, going for a wiki seems the right decision at this point. Changing other things (project management, tickets, source code management) seems not (at least to me; as always YMMV). But we should think about this later! So for the moment, I sugest the following: - leave the SourceForge stuff as is, CVS, mailing lists, trackers, web pages, ... - set up a wiki page for lcd4linux 0.10 documentation - place some links on the SourceForge web site to the wiki - write docs for 0.10 within the new wiki - release 0.10.0 - release 0.10.1 - think about life, the universe, and everything.... What do you think? bye, Michael -- Michael Reinelt <re...@eu...> http://members.eunet.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
|
From: Xavier V. <xav...@fr...> - 2004-12-29 10:57:29
|
Hello Michael, Maxime and the others > Thanks for your mail and your explanations. This sounds great (although > I didn't find the time to have a closer look, for a simple reason: Got > Spellforce: Shadow of Phoenix as a cristmas present :-( Oh no, he got Spellforce-addict once more :) > For we didn't even start writing/changing docs for 0.10, going for a > wiki seems the right decision at this point. Changing other things > (project management, tickets, source code management) seems not (at > least to me; as always YMMV). But we should think about this later! > So for the moment, I sugest the following: > (...) > What do you think? I think we should accept Maxime's invitation and put the wiki there first, then migrate slowly the rest (maybe use the tracker for bug reports, then when releasing final 0.10 move to SVN ...). It would be too much work to set up a wiki at SF, then migrate it to trac. As always, your wish is my command, but I think trac is excellent and I really suggest to migrate to it when we can : - we have to change the website : migrate the website to trac's wiki - we need good bug reporting : use trac's one - .... For the moment, I understand that a total migration may look crasy, so let's go for a partial migration today. Bye ! PS : From tomorrow to Monday, I'm in Spain so I probably won't be able to answer. I think Maxime is more able than me to help the migration to the wiki, and I have full confidence in him. Maxime : I really thank you to help us. If you can't afford giving time for the project, please let me know and we'll discuss about it. -- Xavier VELLO <xav...@fr...> |
|
From: Maxime P. <max...@bu...> - 2004-12-29 16:27:44
|
Hi, > I think we should accept Maxime's invitation and put the wiki there > first, then migrate slowly the rest (maybe use the tracker for bug > reports, then when releasing final 0.10 move to SVN ...). > It would be too much work to set up a wiki at SF, then migrate it to > trac. I've set up a Subversion repository[1] and a Trac environment for LCD4Linux. You can access the LCD4Linux wiki/website at http://lcd4linux.bulix.org I've started gathering some information from the original LCD4Linux website (at SF) and putting them into the new Wiki, as examples. I'll let you do the other pages. I've also created (still for examples) the upcoming 0.10 milestone, and a ticket for this milestone (concerning the documentation needs). In order to complete this setup, I need to know who are the authorized users (both for source commits and for Trac administration), and a password for each of them. For the moment, only me as the administration rights, so that's not very good :) We will discuss about the source tree migration later. > Maxime : I really thank you to help us. If you can't afford giving time > for the project, please let me know and we'll discuss about it. I'm currently on holidays, so there's no problem about it. Enjoy ! - Sam --=20 / Maxime Petazzoni - <max...@bu...> - bulix.org | | Zwe (zwe.bulix.org) - TracTux (https://tractux.bulix.org) | | Gpg Id: 0x83E6AE0D - Jabber: sa...@ja... ________________/ |
|
From: Michael R. <re...@eu...> - 2005-01-06 17:16:46
|
Hi Sam, > I've set up a Subversion repository[1] and a Trac environment for > LCD4Linux. You can access the LCD4Linux wiki/website at > http://lcd4linux.bulix.org Well, this looks absolutely cool! I really love it! > I've started gathering some information from the original LCD4Linux > website (at SF) and putting them into the new Wiki, as examples. I'll > let you do the other pages. Great, thanks! I will look for a wiki crash course, and try to start some pages. > I've also created (still for examples) the upcoming 0.10 milestone, > and a ticket for this milestone (concerning the documentation needs). Hmm, at the moment I'm not going to look into this, as I'm very short of time (as you may have noticed :-) Just finished spellforce, and my real-life job got me again :-( > In order to complete this setup, I need to know who are the authorized > users (both for source commits and for Trac administration), and a > password for each of them. For the moment, only me as the > administration rights, so that's not very good :) But I tried to modify some of the content, looks like this worked? As for the users, is this authorization needed for Wiki editing, or for other stuff? I will send you my username and a password with PM. All other lcd4linux developers who are interested in working with this stuff should do so, too! bye, and thanks again, Michael -- Michael Reinelt <re...@eu...> http://members.eunet.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
|
From: Javi <ja...@gs...> - 2005-01-12 04:01:54
|
=2D----- El Jueves, 6 de Enero de 2005 17:16, Michael Reinelt escribi=F3: -= =2D---- > I've set up a Subversion repository[1] and a Trac environment for > LCD4Linux. You can access the LCD4Linux wiki/website at > http://lcd4linux.bulix.org Hello list. I've submitted some documentation into de wiki page for 'MySQL plugin' and = 'POP3 pluging'. I would appreciated if someone can read/correct it because my english is ve= ry poor and there may be lots of mistakes ;-) Rgds. Javi. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X