Re: Github repository
begin quoting Carlos R. Mafra as of Mon, Nov 18, 2013 at 08:40:42AM +: [chop] It makes review easier and more people see the patches since they don't have to click in some links to open a web browser to see your patches. I don't even read email on a system with a browser. I don't even have the ability to click on links. Click on this link to see $information is an automatic don't-bother on a good day, and a flame in response if I'm feeling a bit stroppy. I didn't invent this procedure, this is the de facto standard submission process among open source projects. This is how wmaker development was always done. And now, out of the blue, you just don't want to send the patches to the mailing list anymore. No, no, no, what's old and proven to work is not the new hotness, and therefore suspect. We must throw out the old and usher in the new era. Also, all the configuration files need to be converted to XML, and the default color scheme should be derived from Fischer-Price or Microsoft, the APIs made compatible with KDE or Gnome, and the whole thing rewritten in Mono and Python. Sheesh. Some people. Keep up with the times, will ya? -- Some days my goal is to ruin a keyboard by way of someone's sinuses. SJS -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
On Mon, 18 Nov 2013 at 1:23:33 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 15:53, Carlos R. Mafra wrote: On Sun, 17 Nov 2013 at 14:34:06 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 13:44, Carlos R. Mafra wrote: On Sun, 17 Nov 2013 at 11:45:23 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 9:37, Carlos R. Mafra wrote: On Sat, 16 Nov 2013 at 23:39:18 +0100, Rodolfo García Peñas wrote: On Thu, 14 Nov 2013, Carlos R. Mafra escribió: I created a wmaker repository in github, https://github.com/crmafra/wmaker I will keep both the old repo.or.cz and the new github updated. Thanks, I am testing it. I sent some patches. Please send the patches to the mailing list. But, If I sent the patches to the mail list, nothing changes. What do you mean by nothing changes? Nothing. My english is too bad, but you cannot understand the difference between you and we. Your project, our project. Again, wmaker is not my project. I guess my agreed-upon status is the maintainer of wmaker, just like you are the maintainer of the wmaker package in the Debian repository. Is the wmaker debian package _your_ project? Or do you consider yourself doing a service to others by being the maintainer of that code in the best possible way as to please the majority of Debian users? The maintainer status is not for life though. If people feel that I'm not capable for maintaining wmaker (for whatever reason) then we can start to discuss who the next maintainer should be and I get out. https://github.com/thekix/wmaker I will upload my work there. If you think my code is ok for *your* project, include it. But couldn't you in addition to the github request also send the patch to the mailing list too? This is what everybody (including you) is doing for the last 5 years and it's working fine. With this move I think you are actively trying to create problems in the established process of patch submission. No. Sorry, but no. If you create a github repo and send a mail to the list pointing it (http://lists.windowmaker.org/dev/msg05993.html): [snip] I thought that I can send the patches in the github repo. I understand what you thought and I tried to explain why you misunderstood it. I don't want disturb you. You are just rioting in the mailing list for no reason and creating disharmony between us, also for no good reason. I tried to explain why the patches must be submitted to the mailing list like everybody is doing for the last 5 years here in wmaker-dev. It makes review easier and more people see the patches since they don't have to click in some links to open a web browser to see your patches. I didn't invent this procedure, this is the de facto standard submission process among open source projects. This is how wmaker development was always done. And now, out of the blue, you just don't want to send the patches to the mailing list anymore. _You_ are not complying with the established rules and you have already shown that you are not willing to cooperate and you are actively trying to create confusion in the wmaker-dev list in the past weeks. Just send the patches to the mailing list. Is that asking too much in a open source project, really? -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
Carlos R. Mafra crma...@gmail.com escribió: [snip] I don't want disturb you. You are just rioting in the mailing list for no reason and creating disharmony between us, also for no good reason. [snip] _You_ are not complying with the established rules and you have already But, where are the rules? Who wrote the rules? Who can change them? shown that you are not willing to cooperate and you are actively trying to create confusion in the wmaker-dev list in the past weeks. I am not creating confusion in the list. I am trying to change things. But, you don't agree with the changes. Why you don't reply other mails? Why you don't reply Christian? Why you don't reply Haroldo, or Paul? Is better say Rodolfo is bad, Rodolfo is rioting the mailing list and don't enter in the real questions. Rodolfo García Peñas (kix) http://www.kix.es/ -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
On Mon, 18 Nov 2013 at 9:38:28 +, Rodolfo García Peñas (kix) wrote: Carlos R. Mafra crma...@gmail.com escribió: [snip] I don't want disturb you. You are just rioting in the mailing list for no reason and creating disharmony between us, also for no good reason. [snip] _You_ are not complying with the established rules and you have already But, where are the rules? Who wrote the rules? Who can change them? wmaker is no different than many other projects out there, and the process is the same. Patches go to the mailing list for discussions. Are you sure you want to question this process? Let me tell you again: _I_ didn't create the concept of discussing patches in a mailing list! I'm just following it because I agree that this is a good way to develop open source software. C'mon Rodolfo. I'm not asking too much, I just want to see the patches in the mailing list (because of reasons I already wrote about). -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
Am 18.11.2013 10:59, schrieb Carlos R. Mafra: But, where are the rules? Who wrote the rules? Who can change them? wmaker is no different than many other projects out there, and the process is the same. Patches go to the mailing list for discussions. Yes, the main thing of a mailinglist is discussion and in a discussion you should try to understand your college even if you disagree to others. Discussion is a way to find compromises, don't you think so ? Are you sure you want to question this process? If our forefathers did never start to 'question processes' we would still try to make fire and we would not sit here and develop software. Things change, new things came along, just as github and if we are not able to check or challenge our processes to easy our work, then we are just stupid. But we are not stupid so we always try to improve our processes, don't you. Let me tell you again: _I_ didn't create the concept of discussing patches in a mailing list! I'm just following it because I agree that this is a good way to develop open source software. Is there a way that github merge request get automatically posted to the list ? If so, then what is the problem then ? C'mon Rodolfo. I'm not asking too much, I just want to see the patches in the mailing list (because of reasons I already wrote about). None wants to stop discussing patches on the list. _You_ started 'github'. Are you now able and ready to make use of _all_ advantages that github is offering ? Let us find a way which is good enough for all, don't you think so ? Kind Regards -- Christian - Please do not 'CC' me on list mails. Just reply to the list :) Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
On Mon, 18 Nov 2013 at 11:30:59 +0100, Christian wrote: Am 18.11.2013 10:59, schrieb Carlos R. Mafra: Let me tell you again: _I_ didn't create the concept of discussing patches in a mailing list! I'm just following it because I agree that this is a good way to develop open source software. Is there a way that github merge request get automatically posted to the list ? If so, then what is the problem then ? That would work just fine, yes. C'mon Rodolfo. I'm not asking too much, I just want to see the patches in the mailing list (because of reasons I already wrote about). None wants to stop discussing patches on the list. _You_ started 'github'. Are you now able and ready to make use of _all_ advantages that github is offering ? I don't agree that moving patch discussion out of the mailing list is an advantage. I created the github in order to _increase_ the options, not to reduce them. I don't mind sending patches via github if people like that too. What I'm against here is to actively avoid sending patches to the mailing list because of github. That does not help. -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
Am 18.11.2013 11:45, schrieb Carlos R. Mafra: On Mon, 18 Nov 2013 at 11:30:59 +0100, Christian wrote: Is there a way that github merge request get automatically posted to the list ? If so, then what is the problem then ? That would work just fine, yes. OK, lets find out if that is possible. C'mon Rodolfo. I'm not asking too much, I just want to see the patches in the mailing list (because of reasons I already wrote about). None wants to stop discussing patches on the list. _You_ started 'github'. Are you now able and ready to make use of _all_ advantages that github is offering ? I don't agree that moving patch discussion out of the mailing list is an advantage. AFAIK it was never a point to move patch discussion out of the mailing list. Discussion about patches should stay in mailing list. I created the github in order to _increase_ the options, not to reduce them. Yes, and this is what we all appreciate, don't we ? And one big advantage is, on github you can see what others are doing cause you can look into their branches. I don't mind sending patches via github if people like that too. What I'm against here is to actively avoid sending patches to the mailing list because of github. That does not help. So we need to find out how we can mail info about 'merge requests' to the mailing list so that this 'merge request' or 'patch' can be discussed. Then all would be happy again or am I wrong here ? And if the discussed patch is OK for acceptance you just need to accept the merge request on github. I think this is an ease for your work, too, isn't it ? Kind Regards -- Christian - Please do not 'CC' me on list mails. Just reply to the list :) Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
On 11/18/2013 10:38 AM, Rodolfo García Peñas (kix) wrote: Why you don't reply other mails? Why you don't reply Christian? Why you don't reply Haroldo, or Paul? Rodolfo, for what it's worth, i don't see why Carlos should have to reply to my input at all. There is no need for him to argue against my input or to even defend his position. I stated my point(s) and provided some food for thought. That's all and enough from my point of view. Whether this will be taken into account or not is not my concern. I was just freely providing my point of view as feedback from one member of the old user base. It was definitely not my intention to impose my position whatsoever. To my understanding, it is not me who is managing this project, but as a very dedicated user of it's outcome i am indebted to provide at least some feedback from my point of view as one of the intended user base. If this is eventually useful or just useless is not to be decided by me. Now for something completely different: I must say that i feel a bit sorry to see these frictions come up on the list. While i believe to understand both Rodolfo and Carlos at the same time, i think there is no need to make a big fuss out of this. Maybe it is already about time to finally arrange some kind of get together or small conference for all involved and interested parties, in order to actually meet and know each other in person? According to my own experience working within virtual teams consisting of members located on different geographical locations and continents during my daily work duties, this can tremenduously help to forge a tighter understanding and feeling for each other and between all people involved in a common project. In the end we are all human beings with a common interest, and it helps to get a better feeling for that. Regards, Paul -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
On 17/11/2013 13:44, Carlos R. Mafra wrote: On Sun, 17 Nov 2013 at 11:45:23 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 9:37, Carlos R. Mafra wrote: On Sat, 16 Nov 2013 at 23:39:18 +0100, Rodolfo García Peñas wrote: On Thu, 14 Nov 2013, Carlos R. Mafra escribió: I created a wmaker repository in github, https://github.com/crmafra/wmaker I will keep both the old repo.or.cz and the new github updated. Thanks, I am testing it. I sent some patches. Please send the patches to the mailing list. But, If I sent the patches to the mail list, nothing changes. What do you mean by nothing changes? Nothing. My english is too bad, but you cannot understand the difference between you and we. Your project, our project. When you send the patch to the mailing list many more people see it and are able to comment on it just by replying a plain text email (that's why the patches must be in the body of the email). That's the purpose of a development mailing list! I thought the idea with github was to have a bug tracking system, not that one could make the visibility of patches lower. If github is only a BTS, we don't use the code review Code review is easy to do over email, that's how things have always worked with many open source projects. I think having the repo in github is a good idea only because John never set up a BTS in www.windowmaker.org. ironic mode onkill John!!ironic mode off nor have our repos for other ideas. Why not? Everybody here in the mailing list have their own repos already in their own machines, that's the nature of distributed development. They develop their own ideas and then send patches, and most of this happens in the privacy of their own machines. Because my local repo is mine and nobody can see it?! _If_ they want to have their ideas in the open, they can have their own repos in github or anywhere else. But that is independent of whether the main wmaker repo is in github or not. Yes, I understand the idea. My code therefore is there. https://github.com/thekix/wmaker I will upload my work there. If you think my code is ok for *your* project, include it. So this argument does not make sense to me. Furthermore, I noticed in your patches that I'd like to fix some typos in the commit logs and to include the WPrefs: prefix in the patch that touches only WPrefs. That will make your repository no longer be in sync with mine after I do that. Yes, my main problem is typos in the commit logs. Other people send patches without commit. It's my fault. For that reason I would think that developing in your own temporary branches (that are later discarded) is more efficient, but everybody has their own workflows and it's ultimately their decision. But again, that is independent of whether the main wmaker is in github or not. Patches belong to the mailing list for everybody to see. I will work in the Debian wmaker package. I will report new bugs here, in the mail list, because That's the purpose of a development mailing list! Thanks and bye. Rodolfo (kix). -- ||// //\\// Rodolfo kix Garcia ||\\// //\\ http://www.kix.es/ -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
On Sun, 17 Nov 2013 at 14:34:06 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 13:44, Carlos R. Mafra wrote: On Sun, 17 Nov 2013 at 11:45:23 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 9:37, Carlos R. Mafra wrote: On Sat, 16 Nov 2013 at 23:39:18 +0100, Rodolfo García Peñas wrote: On Thu, 14 Nov 2013, Carlos R. Mafra escribió: I created a wmaker repository in github, https://github.com/crmafra/wmaker I will keep both the old repo.or.cz and the new github updated. Thanks, I am testing it. I sent some patches. Please send the patches to the mailing list. But, If I sent the patches to the mail list, nothing changes. What do you mean by nothing changes? Nothing. My english is too bad, but you cannot understand the difference between you and we. Your project, our project. Again, wmaker is not my project. I guess my agreed-upon status is the maintainer of wmaker, just like you are the maintainer of the wmaker package in the Debian repository. Is the wmaker debian package _your_ project? Or do you consider yourself doing a service to others by being the maintainer of that code in the best possible way as to please the majority of Debian users? The maintainer status is not for life though. If people feel that I'm not capable for maintaining wmaker (for whatever reason) then we can start to discuss who the next maintainer should be and I get out. https://github.com/thekix/wmaker I will upload my work there. If you think my code is ok for *your* project, include it. But couldn't you in addition to the github request also send the patch to the mailing list too? This is what everybody (including you) is doing for the last 5 years and it's working fine. With this move I think you are actively trying to create problems in the established process of patch submission. I understand that you do want you want with your time, but if you don't send the patches to the wmaker-dev mailing list unfortunately they won't be included in the official repository. I hope you change your mind, you've made a lot of contributions already. -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
Hey guys, please calm down. :) Having code in github is a great idea. You can branch, make changes and submit your code via 'merge requests'. Anybody who is interested to see code changes should then add 'wmaker' to his watch list. Or try to get merge requests automatically mailed to the dev-mailing list and everybody would be happy. I personally think it is an overhead to submit twice. Once as a merge request to wmaker and second mailing it here too. Or just post the link to the merge request here and discuss it. What do you think ? Cheers Chris Am 17.11.2013 15:53, schrieb Carlos R. Mafra: On Sun, 17 Nov 2013 at 14:34:06 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 13:44, Carlos R. Mafra wrote: On Sun, 17 Nov 2013 at 11:45:23 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 9:37, Carlos R. Mafra wrote: On Sat, 16 Nov 2013 at 23:39:18 +0100, Rodolfo García Peñas wrote: On Thu, 14 Nov 2013, Carlos R. Mafra escribió: I created a wmaker repository in github, https://github.com/crmafra/wmaker I will keep both the old repo.or.cz and the new github updated. Thanks, I am testing it. I sent some patches. Please send the patches to the mailing list. But, If I sent the patches to the mail list, nothing changes. What do you mean by nothing changes? Nothing. My english is too bad, but you cannot understand the difference between you and we. Your project, our project. Again, wmaker is not my project. I guess my agreed-upon status is the maintainer of wmaker, just like you are the maintainer of the wmaker package in the Debian repository. Is the wmaker debian package _your_ project? Or do you consider yourself doing a service to others by being the maintainer of that code in the best possible way as to please the majority of Debian users? The maintainer status is not for life though. If people feel that I'm not capable for maintaining wmaker (for whatever reason) then we can start to discuss who the next maintainer should be and I get out. https://github.com/thekix/wmaker I will upload my work there. If you think my code is ok for *your* project, include it. But couldn't you in addition to the github request also send the patch to the mailing list too? This is what everybody (including you) is doing for the last 5 years and it's working fine. With this move I think you are actively trying to create problems in the established process of patch submission. I understand that you do want you want with your time, but if you don't send the patches to the wmaker-dev mailing list unfortunately they won't be included in the official repository. I hope you change your mind, you've made a lot of contributions already. -- Christian - Please do not 'CC' me on list mails. Just reply to the list :) Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
On 17/11/2013 17:24, Christian wrote: Hey guys, please calm down. :) My reply. Having code in github is a great idea. +1 You can branch, make changes and submit your code via 'merge requests'. +1 Anybody who is interested to see code changes should then add 'wmaker' to his watch list. Or try to get merge requests automatically mailed to the dev-mailing list and everybody would be happy. +1 I personally think it is an overhead to submit twice. Once as a merge request to wmaker and second mailing it here too. Or just post the link to the merge request here and discuss it. +1 What do you think ? work twice don't make sense. Cheers Chris Am 17.11.2013 15:53, schrieb Carlos R. Mafra: On Sun, 17 Nov 2013 at 14:34:06 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 13:44, Carlos R. Mafra wrote: On Sun, 17 Nov 2013 at 11:45:23 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 9:37, Carlos R. Mafra wrote: On Sat, 16 Nov 2013 at 23:39:18 +0100, Rodolfo García Peñas wrote: On Thu, 14 Nov 2013, Carlos R. Mafra escribió: I created a wmaker repository in github, https://github.com/crmafra/wmaker I will keep both the old repo.or.cz and the new github updated. Thanks, I am testing it. I sent some patches. Please send the patches to the mailing list. But, If I sent the patches to the mail list, nothing changes. What do you mean by nothing changes? Nothing. My english is too bad, but you cannot understand the difference between you and we. Your project, our project. Again, wmaker is not my project. I guess my agreed-upon status is the maintainer of wmaker, just like you are the maintainer of the wmaker package in the Debian repository. Is the wmaker debian package _your_ project? Or do you consider yourself doing a service to others by being the maintainer of that code in the best possible way as to please the majority of Debian users? The maintainer status is not for life though. If people feel that I'm not capable for maintaining wmaker (for whatever reason) then we can start to discuss who the next maintainer should be and I get out. https://github.com/thekix/wmaker I will upload my work there. If you think my code is ok for *your* project, include it. But couldn't you in addition to the github request also send the patch to the mailing list too? This is what everybody (including you) is doing for the last 5 years and it's working fine. With this move I think you are actively trying to create problems in the established process of patch submission. I understand that you do want you want with your time, but if you don't send the patches to the wmaker-dev mailing list unfortunately they won't be included in the official repository. I hope you change your mind, you've made a lot of contributions already. -- ||// //\\// Rodolfo kix Garcia ||\\// //\\ http://www.kix.es/ -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: Github repository
On 17/11/2013 15:53, Carlos R. Mafra wrote: On Sun, 17 Nov 2013 at 14:34:06 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 13:44, Carlos R. Mafra wrote: On Sun, 17 Nov 2013 at 11:45:23 +0100, Rodolfo García Peñas (kix) wrote: On 17/11/2013 9:37, Carlos R. Mafra wrote: On Sat, 16 Nov 2013 at 23:39:18 +0100, Rodolfo García Peñas wrote: On Thu, 14 Nov 2013, Carlos R. Mafra escribió: I created a wmaker repository in github, https://github.com/crmafra/wmaker I will keep both the old repo.or.cz and the new github updated. Thanks, I am testing it. I sent some patches. Please send the patches to the mailing list. But, If I sent the patches to the mail list, nothing changes. What do you mean by nothing changes? Nothing. My english is too bad, but you cannot understand the difference between you and we. Your project, our project. Again, wmaker is not my project. I guess my agreed-upon status is the maintainer of wmaker, just like you are the maintainer of the wmaker package in the Debian repository. Is the wmaker debian package _your_ project? Or do you consider yourself doing a service to others by being the maintainer of that code in the best possible way as to please the majority of Debian users? The maintainer status is not for life though. If people feel that I'm not capable for maintaining wmaker (for whatever reason) then we can start to discuss who the next maintainer should be and I get out. https://github.com/thekix/wmaker I will upload my work there. If you think my code is ok for *your* project, include it. But couldn't you in addition to the github request also send the patch to the mailing list too? This is what everybody (including you) is doing for the last 5 years and it's working fine. With this move I think you are actively trying to create problems in the established process of patch submission. No. Sorry, but no. If you create a github repo and send a mail to the list pointing it (http://lists.windowmaker.org/dev/msg05993.html): -- 8 -- I created a wmaker repository in github, https://github.com/crmafra/wmaker I will keep both the old repo.or.cz and the new github updated. -- 8 -- I thought that I can send the patches in the github repo. I don't want disturb you. I understand that you do want you want with your time, but if you don't send the patches to the wmaker-dev mailing list unfortunately they won't be included in the official repository. If more people are interested in github, probably they request this method. I hope you change your mind, you've made a lot of contributions already. I hope you change your mind too. -- ||// //\\// Rodolfo kix Garcia ||\\// //\\ http://www.kix.es/ -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
