Hi, I think it's time that we try to come up with a roadmap for the time ahead. There are numerous thing which have been prepared and should be finalized sometimes in the future. The most important ones that come to mind are: 1. New server 2. Structure of the CRUX/CLC project 3. Webpage move/merge (new ports db); things currently missing 4. Short revision control tool discussion (also WRT multiple archs) 5. CVS merge contrib -> opt; core group 6. New contrib collection Less pressing, but also important: - mailing list concept - Introducing subprojects - recruit contributors for subprojects - webpage - ports - tools (self developed stuff) - docs - installer ? - Better responsibilities (kinda goes hand in hand with subprojects) - non-x86 arch handling I added "better responsibilities" since there are certain things which should IMO be defined; e.g. I updated the httpup repos to 2.1, or created the CVS branch for 2.0; both just because I felt it should be done now, and no one else had done it so far (and in the case of httpup people started to wonder...). I don't mind doing those things (also in the future), but I think having a person explicitely in charge would give at least me a better feeling. I'm not sure whether we should organize some IRC/Skype/whatever-meeting or discuss this in the mailing list, but I feel that we should just do it sometimes soon, since there are people actively working on some of these things and I feel bad myself about not providing them more help. So if you have a moment, please take the time to think about the above, and how/whether you'd like to discuss this. Comments appreciated, but not required :-). Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net
hello all. first off i'd like to say hello and thank you for per for making crux. I'm a new reader of the list, but long user of crux and am excited to help the project. I read the email that Johannes has sent out and thought i might put my "newbie" view to the roadmap. 1. New Server - can i ask why? is clc.morpheus.net not sufficient? 2. Structure of the CRUX/CLC project - what is the structure now? is there a good communication between the hierarchy? 3. Webpage move/merge (new ports db); things currently missing - is there a dedicated wiki/webmaster that is supposed to take care of it? 5. CVS merge contrib -> opt; core group - does that mean to actually convert it into one directory? 6. New contrib collection - what can be considered something to add to the new contrib and how does that differ than opt? sorry if that seems kinda basic but i figure what a better place to ask. just my two cents. thanks again guys. -J On Apr 29, 2005, at 10:12 AM, Johannes Winkelmann wrote:
Hi,
I think it's time that we try to come up with a roadmap for the time ahead. There are numerous thing which have been prepared and should be finalized sometimes in the future. The most important ones that come to mind are:
1. New server 2. Structure of the CRUX/CLC project 3. Webpage move/merge (new ports db); things currently missing 4. Short revision control tool discussion (also WRT multiple archs) 5. CVS merge contrib -> opt; core group 6. New contrib collection
Less pressing, but also important: - mailing list concept - Introducing subprojects - recruit contributors for subprojects - webpage - ports - tools (self developed stuff) - docs - installer ? - Better responsibilities (kinda goes hand in hand with subprojects) - non-x86 arch handling
I added "better responsibilities" since there are certain things which should IMO be defined; e.g. I updated the httpup repos to 2.1, or created the CVS branch for 2.0; both just because I felt it should be done now, and no one else had done it so far (and in the case of httpup people started to wonder...). I don't mind doing those things (also in the future), but I think having a person explicitely in charge would give at least me a better feeling.
I'm not sure whether we should organize some IRC/Skype/whatever-meeting or discuss this in the mailing list, but I feel that we should just do it sometimes soon, since there are people actively working on some of these things and I feel bad myself about not providing them more help. So if you have a moment, please take the time to think about the above, and how/whether you'd like to discuss this. Comments appreciated, but not required :-).
Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net _______________________________________________ clc-devel mailing list clc-devel@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-devel
Hy Jonathan, On Fri, Apr 29, 2005 at 15:04:48 -0500, Jonathan Asghar wrote:
hello all. first off i'd like to say hello and thank you for per for making crux.
I'm a new reader of the list, but long user of crux and am excited to help the project. I read the email that Johannes has sent out and thought i might put my "newbie" view to the roadmap. 1. New Server - can i ask why? is clc.morpheus.net not sufficient? Well, morpheus.net was never really meant as a permanent solution, even
2. Structure of the CRUX/CLC project - what is the structure now? is there a good communication between the hierarchy? Currently, CLC is a completely separate project (own webpage, own CVS etc.) so a structure is yet to be defined. Regarding communication: I
Welcome and thanks for the nice words! though it's been a great temporary one. The idea is to merge the webpages of crux and clc to avoid further confusion for the users; a common webpage will allow to point users to a single URL for both crux (the core) and the additional stuff we do at CLC. think it's working fine, with the issues all public projects of a certain size face: timezone differences, (non-crux)work load and so on.
3. Webpage move/merge (new ports db); things currently missing - is there a dedicated wiki/webmaster that is supposed to take care of it? Might be a good idea; Simone is currently running some test (you can find more info on this in the mailing list archive).
5. CVS merge contrib -> opt; core group - does that mean to actually convert it into one directory? That's the plan, yes
6. New contrib collection - what can be considered something to add to the new contrib and how does that differ than opt? the new contrib will be a merged collection of httpup repositories, maintained by our users. There's quite a lot on that in the archives of this list, too: https://lists.berlios.de/pipermail/clc-devel/2004-September/000601.html should give you an idea of the concept ('people' there refers to the new contrib collection).
sorry if that seems kinda basic but i figure what a better place to ask. just my two cents. I hope I could make some things clearer :-)
Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net
On 04/29/05 17:12 Johannes Winkelmann wrote:
I think it's time that we try to come up with a roadmap for the time ahead.
[cut]
I'm not sure whether we should organize some IRC/Skype/whatever-meeting or discuss this in the mailing list, but I feel that we should just do it sometimes soon, since there are people actively working on some of these things and I feel bad myself about not providing them more help. So if you have a moment, please take the time to think about the above, and how/whether you'd like to discuss this. Comments appreciated, but not required :-).
I think a realtime meeting (IRC or something) is the best option: during the last weeks discussion on the ML has proved a bit slow; I'd opt for something more immediate at least for this occasion, since I believe some choice / plan has to be made ASAP to avoid confusion, unnecessary work, etc. Any suggestion for date, time and media is welcome. Regards, Simone. -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip@varlock.com
Hi, On Sun, May 01, 2005 at 19:12:34 +0200, Simone Rota wrote:
[cut]
I'm not sure whether we should organize some IRC/Skype/whatever-meeting or discuss this in the mailing list, but I feel that we should just do it sometimes soon
I think a realtime meeting (IRC or something) is the best option [...] Any suggestion for date, time and media is welcome. I'd suggest we do a "bug squishing day" inspired by debian and others, where we all meet in a special IRC room (#crux-bugs) to discuss things like adapting ports from former maintainers, webpage move and similar issues. We might also go for a whole weekend to make sure everyone has the chance to drop by once.
What about next weekend (either Tue-Fri-Sat, or Fri-Sat-Sun)? Would that work for you guys? Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net
Johannes Winkelmann wrote:
What about next weekend (either Tue-Fri-Sat, or Fri-Sat-Sun)? Would that work for you guys?
This weekend is OK for me too. Regards Till -- http://www.tbmnet.de
On Mon, 9 May 2005, Johannes Winkelmann wrote:
I'd suggest we do a "bug squishing day" inspired by debian and others, where we all meet in a special IRC room (#crux-bugs) to discuss things like adapting ports from former maintainers, webpage move and similar issues. We might also go for a whole weekend to make sure everyone has the chance to drop by once.
Good idea!
What about next weekend (either Tue-Fri-Sat, or Fri-Sat-Sun)? Would that work for you guys?
This weekend OK for me. We should also setup a IRC log for the channel during the days as a reference to re-collect the ideas after the meeting. (and for people coming in the 2nd and 3rd day) Regards, Simone
If you guys are or with it, count me in, i'd love to help! (even if i am a "newbie") ;) -J
participants (4)
-
Johannes Winkelmann
-
Jonathan Asghar
-
Simone Rota
-
Till Biedermann