Heinz-M. Graesing schreef:
Hello list members,
After the latest developments on the list, we've received a lot of complaints about the how this list is being used. Tobias - a member of Linux4Afrika - offered his help to improve the communication of this project. Please have a look at www.linux4afrika.de. Linux4Afrika still offers the best x2go tutorials on the net. We also got help through Mike Gabriel (a member of the x2go-dev list -> das-netzwerkteam.de ). Thank you very much!
From now on we'll change some rules of communication on this project:
- x2go-dev list the x2go-dev list is reserved for all development topics. There will be no discussion on topics like "organisational criticism" or "personal preferences".
This is the excisting list, isn't it?
- x2go-user list The x2go-user list is reserved for all user topics. Please also avoid topics like "organisational criticism" or "personal preferences". On the x2go-user list people may ask their questions on setting up working x2go environments, share their problems when using the x2goclient etc. This list will be co-moderated by Tobias. Please use acurate mail subjects and don't discuss "Off Topic" .
I think it's important that X2go has a friendly community. The last time I see some people here who are a bit less friendly, I don't like subjects as "hello dead project" or people who cannot wait till something is done.
Maybe it's good to have somebody who does something when people are not-so-friendly, But not sure if that's what you mean with "co-moderated".
- x2go-announcements list there will be a new group called "x2go-announcements" too. This group is READ ONLY. On this group announcements will be made. When ever it's possible we will connect the information with a DATE so you can use it for your concepts. We will do our best to give you timelines and time frames whenever possible. If we realize that plans and actions get delayed, we will inform you as soon as we know about it, so that you can adopt your own schedules. We hope to meet your requirements with this change. Please, make sure that you subscribe to the x2go-announcements list to benefit from this.
When I were you, I would not set so many dates. Tell it when something is ready ;-) Planning software-projects is very difficult. But, for some people it's good to have deadlines.
Don't you forget Gmane?
- the GIT repository
In the future we will change our workflow as follows. We (Alex and Heinz) will use an internal GIT repository for drafts, collecting new ideas, internal testing, etc. This will be our sandbox, we do not want to bother you with that.
We will also push our work to a public GIT repository in regular, sensible intervals. This will always be the latest functional x2go code available (HEAD).
This shall give the online community convenient access to our work. As some of you have suggested, we will fill the GIT master branch with the x2go core components. The community, however, will have access to custom GIT branches), to work on their own blend. This will enable us to cooperate and benefit from each others' work.
Hmm, not sure how other teams do this. I think it would be more nice when it would be possible to work directly in the public GIT and to make packages and tarrballs when it's ready. I think it would be nice if the devel-team would grow slowly from 2 to more people. But it takes time.
But I think maybe you want to develop sometimes for a paying customer who wants to be the first with a feature, giving it a bit later to the comunity. In such a case you need a private GIT.
It will not be easy to grow from a private project to something what's bigger and more open. Maybe it's good to talk to somebody with more expierence on that, maybe that person could also monitor the list and the GIT to give you advice. Sometimes you will have to say "no" to patches, and for some things you even don't have the time to study it...
Thanks for all your work on X2go!
With regards, Paul van der Vlis.