<div class="gmail_quote">On Sat, Feb 9, 2013 at 12:33 AM, Carl Worth <<a href="mailto:cworth@cworth.org" target="_blank">cworth@cworth.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">José Fonseca <<a href="mailto:jose.r.fonseca@gmail.com">jose.r.fonseca@gmail.com</a>> writes: > What about issues reports, e.g, > <a href="https://github.com/apitrace/apitrace/issues/107" target="_blank">https://github.com/apitrace/apitrace/issues/107</a> . Can you comment, or > should I? </div>I just commented there. I even turned on watching so hopefully I'll be able to pick up on new issues that I should "own" as well. <div class="im"> > Fact is that I already lost more data/scripts on *.<a href="http://freedesktop.org" target="_blank">freedesktop.org</a> > alone (due to hardware failures) than on any non-free code hosting > services over the last 15 years. Partly my fault because I didn't > backup every single thing but that's my point: with the non-free > services I never felt the need to backup anything more than the code. </div>I agree that you'll get better service by paying for it. And I don't have any problem with services being rendered for a fee. The things I don't like are services extracting value from locking up my data, or from locking me out of the source code used to manipulate my data. <div class="im"> > Yes. I do it all the time. website and wiki are just another git > repos. </div>That's good to know. I missed the "git access" link when I looked at the wiki earlier. And this actually looks like a nice git-backed markdown-based wiki. I've used ikiwiki for similar things, but have often been annoyed with various quirks it has to be tempted to write a replacement. Anyway, a git-based wiki like this would make it easy for me to, for example, rename retrace->replay throughout the wiki. That's good. (Though, with your new plan, there's less of that needed.) <div class="im"> > Not the whole website itself. But they seem to maintain repositories > for many components/technologies they use on <a href="https://github.com/github" target="_blank">https://github.com/github</a> </div>Oh, very cool. Thanks for pointing that out. I found git-flavored-markdown, redcarpet, sundown, and gollum all in there. So maybe I just found my replacement for ikiwiki already. Hurrah! So it does look like the wiki portions, at least, are all implemented with free software. So that much of github looks totally compliant with my criteria. Cool. It's not as clear that the issue tracker is as compliant... <div class="im"> > And github doesn't even seem to fare that bad according to your own > standards. </div>Even better than I realized. Thanks for educating me. <div class="im"> > Anyway, I don't hope to convince you, but it would be great if you > could own issues on apitrace components you maintain. But no biggie if > you don't. Just want to know what I can expect. </div>I'll be glad to. I do tend to really dislike web-based forums for things like polling for open issues looking for work I'd like to do, (but I appreciate how this can simplify things for users and make them more likely to report issues). So my tendency would be to convert open issues into items on a todo list. Something like: Issue #107 ---------- "apitrace trim --deps" leaves out glTexImage calls for GL_TEXTURE_CUBE_MAP_POSITIVE/NEGATIVE_X/Y/Z. Asked for example trace in the thread on the github tracker. If you wouldn't mind me maintaining items like that, then I could do that in ToDo.md in the wiki. And then it would be more convenient for me to push instead of sending wiki edits as git patches. </blockquote><div> Sure. Note the Todo list is now split as one page per component (e.g ToDoCLI.md ) </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> My username on github is cworth-gh if you'd like to grant me permission for doing that. </blockquote></div> Done. Let me know if you run into issues. Thanks Carl! Jose