Hi there,
On So 18 Jul 2010 08:57:10 CEST "John A. Sullivan III" wrote:
On Sun, 2010-07-18 at 01:17 +0200, Jörg Sawatzki wrote:
<snip>
> We are working with git and now that is a big whish of you, the next
> thin we'll do is to get git.x2go.org working.
Why don't you use github or *forge? It saves time and money and you have
the same (and more) possibilities than with your own server.
Apart from that, you'd have to setup a bug tracker, wiki and stuff like
that as well - and run, administer, update and maintain it. I'd rather
invest my time to get on with development instead of reinventing the
wheel at this point. :)
> We wan't to use our own server to be able to autobuild packages etc...
> but I will push a copy to github too.
There is absolutely no need for this - for example, if you have a
project page on Launchpad, their servers can autobuild .deb packages for
you - for all kinds of architectures and ubuntu/debian versions.
If you still want to build packages on your own server, just build them
from the github/*forge repository.
Of course it is up to you - but keep in mind that it will cost you a lot
more time (and money) to build and run an infrastructure that is as good
or better than what all these *forge sites offer you for free.
<snip>
I second that idea. One can lose countless, priceless development hours
learning, building, maintaining, and handling the inevitable
catastrophes of one's own infrastructure - John
Silently thinking by myself: ,,Running one's own servers... I can hear
the system administrator's heart speak. As sysadmins, we like to be in
control of our resources ;-) (even if they crash weekly :-O ). In
resonance, Mike''
1.
Heinz said that he prefers to build the Debian packages on their own
servers...
Nonetheless, people here provide reasons why a *forge site is better
etc. I think before providing suggestions and giving all sorts of good
advice, we should ask Heinz and Alex, why they prefer building
packages on their servers.
If we know the answer---and it might be a very reasonable one---then
maybe we understand their preferences or even worries and we don't
have to haggle (,,feilschen'' in German) concerning this point.
2.
Heinz and Alex are close to the next x2go release. I think, we are
definitely delaying them with our ideas and list postings. I think
that discussing project structures before the release is nice but
counter-productive. A possible focus could be:
1. support the next release as best as we can (testing, bug reports etc.)
2. be happy once the release is out
3. ONLY THEN: take our time to listen to each others ideas, find a synthesis
of them all and setup a working scenario that allows fluid collaboration,
coordinated by the core developers of X2go
Doing all this simultaneously (as we do currently) feels very chaotic
and not really supportive to me.
3.
We should not mix up the source development and the package
maintenance for the various distribution (AFAIK *forge is for source
code development, launchpad's ppa for Ubuntu package development etc.
Canonical's Launchpad does not build Debian packages IMHO). Once there
is a sensible point of time for this discussion i may enlarge on that.
Greetins to all,
Mike
--
DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419
eMail-LeseSchreibStunde: wochentags 8h-10h
mail: [email protected], http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
_______________________________________________
X2go-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/x2go-dev
