<div dir="ltr">The summary is accurate from my viewpoint. I knew months ago that Richard had put the repository on Github, but the knowledge was old and I didn't realize bad. So after FOSDEM I went straight to Github. It would have taken really big red flags for me to wake up and realize that I was in the wrong place. I ultimately figured it out because of the reference to Gitorious in the license itself.<div>
<br></div><div style>I was wrong in my dent when I said I downloaded from Github; I didn't, I edited right on Github. Upon realizing my error, I then dutifully downloaded from Gitorious and started over. As explained when I submitted to Github, the problem was that I couldn't figure out how to get the changes from my computer to Gitorious to ask for a merge, and I also suspect I probably also have it all configured wrong on my computer anyway. At that point I just gave up. I figured it was going to take me yet several more hours to figure it out, and while I considered it a worthwhile effort, I didn't have that time at the moment and wanted to wrap up my task and provide feedback after FOSDEM in a timely manner. Therefore the fateful decision to submit on Github.</div>
<div style><br></div><div style><br></div><div style>Pam</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Feb 8, 2013 at 8:36 AM, Bradley M. Kuhn <span dir="ltr"><<a href="mailto:bkuhn@ebb.org" target="_blank">bkuhn@ebb.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Stephen Michael Kellat wrote at 22:14 (EST) on Thursday:<br>
<div class="im">> Please do also disclose a summary of your sidebar discussion with<br>
> Richard Fontana as well as Claes Wallin that appears to be happening<br>
> on Identica and other federated StatusNet sites.<br>
<br>
</div>Stephen, since that discussion is public, I am pretty sure it's not an<br>
HBR violation to discuss copyleft-next on <a href="http://identi.ca" target="_blank">identi.ca</a>, since it's a public<br>
forum. But I see your point (more on that below).<br>
<br>
Meanwhile, my understanding of the <a href="http://identi.ca" target="_blank">identi.ca</a> conversation is this:<br>
<br>
* Pam Chestek got copyleft-next off GitHub, and nothing there told her<br>
GitHub wasn't the canonical location for participation (this should<br>
be fixed immediately, IMO. I realize the README says it, but there<br>
should be something in big bold letters on GitHub: THIS IS A MIRROR<br>
ONLY. DO NOT SUBMIT PULL REQUESTS AND ISSUES HERE. USE MAILING LIST<br>
AND GITORIOUS [or whatever solution Fontana decides].<br>
Ideally, the pull request/issue tracker should be turned off.<br>
<br>
* Pam realized, probably after getting the checkout and seeing the<br>
readme, that Gitorious was preferred.<br>
<br>
* Pam couldn't submit changes via Gitorious (at that point, presumably<br>
her tracking branches were all pointed at GitHub, which was probably<br>
part of the problem).<br>
<br>
* Fontana opened an issue on GitHub to collaborate with Pam on the<br>
issue she raised.<br>
<br>
* I theorized that this marked a distributing occurrence, since GitHub<br>
instance of copyleft-next seemed to be active again instead of just being a<br>
mirror. I complained heavily to Fontana about it, and Fontana<br>
countered with what I believed were incorrect analogies to GPLv3<br>
drafting process (i.e., I thought copyleft-next was trying to avoid<br>
those, anyway!)<br>
<br>
<br>
Pam and Fontana, is that summary accurate from your point of view?<br>
<div class="im"><br>
> I am minded at this point to ask that the folks who find the need to<br>
> use GitHub please make themselves heard on list within our primary<br>
> record of communications. The mailing list has functioned quite well<br>
> as a de facto issue tracker thus far and I do not enjoy the notion of<br>
> having to chase down discussion across multiple fora.<br>
<br>
</div>This is a good point. I'll try to avoid using <a href="http://identi.ca" target="_blank">identi.ca</a> to discuss<br>
copyleft-next in future.<br>
<br>
I do agree that having to follow GitHub, <a href="http://identi.ca" target="_blank">identi.ca</a>, Gitorious, and this<br>
mailing list is annoying. While HBR doesn't prohibit it, I suggest we<br>
all work to restrain ourselves to use *only* the mailing list and<br>
Gitorious and nothing else for now, to avoid people having to track so<br>
many fora.<br>
<br>
I have *so* little time for copyleft-next, thus I really am swayed by<br>
Stephen's point here. I had assumed that checking the git log from<br>
Gitorious and reading mailing list traffic would be adequate any time I<br>
had a moment to check in with copyleft-next. If that's not true:<br>
because of use of GitHub, <a href="http://identi.ca" target="_blank">identi.ca</a>, or any other fora being used, we<br>
may want to nip it -- not because it's an HBR violation or even because<br>
one of those solutions is proprietary (<a href="http://identi.ca" target="_blank">identi.ca</a> isn't after all), but<br>
because it makes it difficult to follow a conversation across so many<br>
fora.<br>
<br>
I hadn't realized how big of a problem that is for people who have<br>
limited time for the project until Stephen raised it. Thanks for<br>
raising that point.<br>
<span class="HOEnZb"><font color="#888888">--<br>
</font></span><div class="HOEnZb"><div class="h5"> -- bkuhn<br>
_______________________________________________<br>
copyleft-next mailing list<br>
<a href="mailto:copyleft-next@lists.fedorahosted.org">copyleft-next@lists.fedorahosted.org</a><br>
<a href="https://lists.fedorahosted.org/mailman/listinfo/copyleft-next" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/copyleft-next</a><br>
</div></div></blockquote></div><br></div>