Menu
▾
▴
tuxmath-devel
|
From: Bastien <bz...@gn...> - 2016-04-18 10:05:58
|
Hi all, I'm copying Deepak who kindly invited me to contribute to the Github tux4kids repositories here: https://github.com/tux4kids/ What are the relationships between the Github Tux4Kids repositories and the ones on Alioth? Which ones are upstream? I see https://github.com/tux4kids/tux4kids-web displays my commit so I assume the alioth repos are the ones upstream as advertized on the website. If we are to boost tux4kids development again, it'd be nice to have some clarity here, otherwise we will lose too much energy. Thanks to anyone who can shed some light on this! Best, -- Bastien |
|
From: Holger L. <ho...@la...> - 2016-04-18 10:43:47
Attachments:
signature.asc
|
Hi, On Mon, Apr 18, 2016 at 12:05:38PM +0200, Bastien wrote: > I'm copying Deepak who kindly invited me to contribute to the Github > tux4kids repositories here: https://github.com/tux4kids/ > > What are the relationships between the Github Tux4Kids repositories > and the ones on Alioth? Which ones are upstream? > > I see https://github.com/tux4kids/tux4kids-web displays my commit so > I assume the alioth repos are the ones upstream as advertized on the > website. > > If we are to boost tux4kids development again, it'd be nice to have > some clarity here, otherwise we will lose too much energy. oh dear ;) I fully agree on the "we need clarity" and we need to decide on this. I'd propose "those who do, decide", though if there is a change, this change needs to be documented too. That said, if github and alioth need to be kept in sync manually, I'd be glad to setup some jobs on jenkins.debian.net which will notify us, if the repos are out of sync. Better yet: keep them in sync automatically. -- cheers, Holger (who doesnt want to get involved too much into the "upstream" side of tux4kids. I'll happily continue packaging tuxtype+tuxmath (and thus t4k-common) for Debian though…) |
|
From: deepak a. <dee...@gm...> - 2016-04-19 09:37:09
|
Hi Guys Sorry I was traveling for the past few weeks and have very limited internet connectivity. After discussing with the other mentors and contributors, we have decided to use Github for day to day development and alioth for release. @Bastien: I used Github importer for moving code recently, that's why it has your latest commit. So this is how things will work. 1. Every contributor will fork main repository and will work on individual copy and send us a pull request. 2. After verifying we will merge code in it's corresponding branch 3. While releasing new code development branch will be merge with the master and the new code will be pushed to alioth. If you guys can add anything which I haven't covered that will be great. @ Holger If we can automate code synchronisation of Github master with the alioth master branch that would be great. I will drop an email on each and every discussion making list after we finalise things and will document all the details in the read me section as well as on the main website. On Mon, Apr 18, 2016 at 4:13 PM, Holger Levsen <ho...@la...> wrote: > Hi, > > On Mon, Apr 18, 2016 at 12:05:38PM +0200, Bastien wrote: > > I'm copying Deepak who kindly invited me to contribute to the Github > > tux4kids repositories here: https://github.com/tux4kids/ > > > > What are the relationships between the Github Tux4Kids repositories > > and the ones on Alioth? Which ones are upstream? > > > > I see https://github.com/tux4kids/tux4kids-web displays my commit so > > I assume the alioth repos are the ones upstream as advertized on the > > website. > > > > If we are to boost tux4kids development again, it'd be nice to have > > some clarity here, otherwise we will lose too much energy. > > oh dear ;) > > I fully agree on the "we need clarity" and we need to decide on this. > I'd propose "those who do, decide", though if there is a change, this > change needs to be documented too. > > That said, if github and alioth need to be kept in sync manually, I'd be > glad to setup some jobs on jenkins.debian.net which will notify us, if > the repos are out of sync. Better yet: keep them in sync automatically. > > > -- > cheers, > Holger (who doesnt want to get involved too much into the > "upstream" side of tux4kids. I'll happily continue > packaging > tuxtype+tuxmath (and thus t4k-common) for Debian though…) > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications > Manager > Applications Manager provides deep performance insights into multiple > tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > Tuxmath-devel mailing list > Tux...@li... > https://lists.sourceforge.net/lists/listinfo/tuxmath-devel > > |
|
From: Holger L. <ho...@la...> - 2016-04-19 09:44:38
Attachments:
signature.asc
|
Hi, On Tue, Apr 19, 2016 at 03:07:02PM +0530, deepak aggarwal wrote: > After discussing with the other mentors and contributors, we have decided > to use Github for day to day development and alioth for release. where did this discussion take place? > So this is how things will work. > 1. Every contributor will fork main repository and will work on individual > copy and send us a pull request. > 2. After verifying we will merge code in it's corresponding branch > 3. While releasing new code development branch will be merge with the > master and the new code will be pushed to alioth. do you plan to merge in master only for releases or all the time? I'd propose to "all the time". (And use tags for releases.) > @ Holger If we can automate code synchronisation of Github master with the > alioth master branch that would be great. I think we first need to agree on the question above. So far I was rather thinking about a notification if repos are not in sync… not automated pushing. (Also this would need to happen on the side of the people pushing to github…) > I will drop an email on each and every discussion making list after we > finalise things and will document all the details in the read me section as > well as on the main website. again: what other discussion list exists? -- cheers, Holger |
|
From: deepak a. <dee...@gm...> - 2016-04-19 10:27:00
|
On Tue, Apr 19, 2016 at 3:14 PM, Holger Levsen <ho...@la...> wrote: > Hi, > > On Tue, Apr 19, 2016 at 03:07:02PM +0530, deepak aggarwal wrote: > > After discussing with the other mentors and contributors, we have > decided > > to use Github for day to day development and alioth for release. > > where did this discussion take place? Over hangout as it's the quickest. > > So this is how things will work. > > 1. Every contributor will fork main repository and will work on > individual > > copy and send us a pull request. > > 2. After verifying we will merge code in it's corresponding branch > > 3. While releasing new code development branch will be merge with the > > master and the new code will be pushed to alioth. > > do you plan to merge in master only for releases or all the time? I'd > propose to "all the time". (And use tags for releases.) > ya that would be a better thing. > > > @ Holger If we can automate code synchronisation of Github master with > the > > alioth master branch that would be great. > > I think we first need to agree on the question above. So far I was > rather thinking about a notification if repos are not in sync… not > automated pushing. (Also this would need to happen on the side of the > people pushing to github…) > > > I will drop an email on each and every discussion making list after we > > finalise things and will document all the details in the read me section > as > > well as on the main website. > > again: what other discussion list exists? I was referring individual mailing list of tuxmath, tuxpaint, tuxtype etc. > > > -- > cheers, > Holger > |
|
From: Holger L. <ho...@la...> - 2016-04-19 10:58:45
Attachments:
signature.asc
|
On Tue, Apr 19, 2016 at 03:56:52PM +0530, deepak aggarwal wrote: > On Tue, Apr 19, 2016 at 3:14 PM, Holger Levsen <ho...@la...> > > On Tue, Apr 19, 2016 at 03:07:02PM +0530, deepak aggarwal wrote: > > > After discussing with the other mentors and contributors, we have > > decided to use Github for day to day development and alioth for release. > > where did this discussion take place? > Over hangout as it's the quickest. :-( it also is rather exclusive, mail is much more inclusive, as it allows offline participation & is more accessible to many (think shy people or people less fluent in spoken words in a foreign languages). and (i'm pretty sure but surely might have missed it) you didnt once mention on the tuxmath + tuxtype list that there is a hangout "group"(?) for tux4kids… :/ I've wondered several times where gsoc coordination for tux4kids happened, as it evidently did, even though there werent't any traces on the lists I read… Bastien: (indepent of any hangouts) I btw think that we miss one list tux4kids-devel - we only have tux4kids-tuxtype-dev and tuxmath-devel… And we probably miss and up2date authoritive source which lists and other communication media exist. -- cheers, Holger |
|
From: deepak a. <dee...@gm...> - 2016-04-19 12:40:38
|
On Apr 19, 2016 4:28 PM, "Holger Levsen" <ho...@la...> wrote: > > On Tue, Apr 19, 2016 at 03:56:52PM +0530, deepak aggarwal wrote: > > On Tue, Apr 19, 2016 at 3:14 PM, Holger Levsen <ho...@la...> > > > On Tue, Apr 19, 2016 at 03:07:02PM +0530, deepak aggarwal wrote: > > > > After discussing with the other mentors and contributors, we have > > > decided to use Github for day to day development and alioth for release. > > > where did this discussion take place? > > Over hangout as it's the quickest. > > :-( it also is rather exclusive, mail is much more inclusive, as it > allows offline participation & is more accessible to many (think shy > people or people less fluent in spoken words in a foreign languages). > and (i'm pretty sure but surely might have missed it) you didnt once > mention on the tuxmath + tuxtype list that there is a hangout "group"(?) > for tux4kids… :/ Ya actually a lot of things are still fragmented right now. Discussion list is one of them. > > I've wondered several times where gsoc coordination for tux4kids > happened, as it evidently did, even though there werent't any traces on > the lists I read… Actually there is a Tux4Kids-mentor Google group where GSoc coordination occurs. We are using it for the past few year but we delete old threads whenever new GSoc starts. So you wont be able to read previous years thread. > Bastien: (indepent of any hangouts) I btw think that we miss one list > tux4kids-devel - we only have tux4kids-tuxtype-dev and tuxmath-devel… > > And we probably miss and up2date authoritive source which lists and > other communication media exist. > > > -- > cheers, > Holger |
|
From: Bastien G. <bz...@gn...> - 2016-04-19 15:23:50
|
Hi all, thanks for these clarifications, very interesting. I'm in favor of using free softwares as much as possible and of using a very limited set of inclusive communication tools. Using the debian repositories and a single mailing for all projects would do IMHO*. I very much agree with Holger about emails being more inclusive then Hangout, both by design and because Hangout is not free. I understand the idea of using github for the repos, and that's not a real problem if you decide to go this way. But I don't think using Hangout and Googles Groups is a good idea: it's not free software and it splits the attention into many tools. Anyway, back to my initial concern: Deepak, are you the official maintainer for the Tux* projects? If so, can you summarize the decisions on the repositories and the communication channels so that I advertize it accurately on the website? Thanks in advance! * I don't like *-devel@ mailing lists: users and developers should talk to eachother in a single canal. Remember the "you-don't-have-a scalability-problem-yet" principle? Same goes for communication: as long as you don't need to split your lists for various audiences, just use one list. I guess 99% the -devel* mailing lists spread years ago just by imitation, because it seemed a well-established practice. -- Bastien |
|
From: scottmc <sco...@gm...> - 2016-04-19 20:41:52
|
On Tue, Apr 19, 2016 at 8:23 AM, Bastien Guerry <bz...@gn...> wrote: > Hi all, > > thanks for these clarifications, very interesting. > > I'm in favor of using free softwares as much as possible and of using > a very limited set of inclusive communication tools. > > Using the debian repositories and a single mailing for all projects > would do IMHO*. > > I very much agree with Holger about emails being more inclusive then > Hangout, both by design and because Hangout is not free. > > I understand the idea of using github for the repos, and that's not a > real problem if you decide to go this way. > > But I don't think using Hangout and Googles Groups is a good idea: > it's not free software and it splits the attention into many tools. > > Anyway, back to my initial concern: Deepak, are you the official > maintainer for the Tux* projects? > > If so, can you summarize the decisions on the repositories and the > communication channels so that I advertize it accurately on the > website? > > Thanks in advance! > > > * I don't like *-devel@ mailing lists: users and developers should > talk to eachother in a single canal. Remember the "you-don't-have-a > scalability-problem-yet" principle? Same goes for communication: as > long as you don't need to split your lists for various audiences, just > use one list. I guess 99% the -devel* mailing lists spread years ago > just by imitation, because it seemed a well-established practice. > > -- Copying the other mailing lists that I know of. Deepak is moving our repos all over to github so that they will be all in one location instead of scattered amongst several websites. URL is https://github.com/tux4kids The Hangout was started by the Tux4Kids admin and is just those who are signed up to be GSoC mentors for this year. Same with the private google group mailing list. We use it to discuss the 100+ proposals we receive each year, to narrow those down to the number of slots that Google allocates for us. I agree, we should narrow the mailing lists down to just a tux4kids general mailing list instead of one for tuxtyping, tuxpaint, tuxmath, etc. Perhaps we just move over to using tux4kids-discuss? Also the setting on the mailing lists here seem to be a bit weird, they should default the reply to to be back to the mailing list and not to just the previous author. Who is the admin who can fix that? It's annoying. We should also require our GSoC students to post bi-weekly updates either to the mailing list or a blog posting on the Github Tux4Kids site. This year we will be able to keep a closer watch on the code commits with the projects all hosted in the same place. It was confusing to potential new students to figure out where our code was and which repos were the current ones. Hopefully this will also open the door to others to submit pull requests with fixes. More discussion probably needs to take place on how our workflow should be done, such as who will maintain each of the projects, and accept/reject pull requests, etc. -Scott |
|
From: Bastien G. <bz...@gn...> - 2016-04-19 21:23:14
|
Hi Scott, thanks for your input. scottmc <sco...@gm...> writes: > The Hangout was started by the Tux4Kids admin and is just those who > are signed up to be GSoC mentors for this year. Same with the > private google group mailing list. We use it to discuss the 100+ > proposals we receive each year, to narrow those down to the number of > slots that Google allocates for us. Fait enough, thanks for the explanation. > I agree, we should narrow the mailing lists down to just a tux4kids > general mailing list instead of one for tuxtyping, tuxpaint, tuxmath, > etc. Perhaps we just move over to using tux4kids-discuss? That'd be good, yes. > Also the setting on the mailing lists here seem to be a bit weird, > they should default the reply to to be back to the mailing list and > not to just the previous author. Who is the admin who can fix > that? It's annoying. (The current setting is the good one: it's more annoying to send private emails to everybody than to send a collective message to just someone... and it's really a matter of hitting the right button in your email client.) > We should also require our GSoC students to post bi-weekly updates > either to the mailing list or a blog posting on the Github Tux4Kids > site. Yes, that'd be great! Just posting an email on a public mailing list would be good -- then they can publish it on a blog, on github, where they want really. > This year we will be able to keep a closer watch on the code > commits with the projects all hosted in the same place. It was > confusing to potential new students to figure out where our code was > and which repos were the current ones. Hopefully this will also open > the door to others to submit pull requests with fixes. More > discussion probably needs to take place on how our workflow should be > done, such as who will maintain each of the projects, and accept/ > reject pull requests, etc. I'm glad to see the collective energy for moving things forward into the right direction! This will help a lot for newcomers. Thanks! -- Bastien |
×
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