[Owncloud] bugtracker situation

[MJ Ray]

Frank Karlitschek <frank at owncloud.org>
> On 22.10.2012, at 21:39, kpneal at pobox.com wrote:
> >> On 22.10.2012, at 19:04, MJ Ray <mjr at phonecoop.coop> wrote:
> >>> See https://github.com/site/terms or for a summary
> >>> http://tos-dr.info/#github-tosdr
> > I'd like to look at the ToS but the above URL isn't working at the moment.

It's back now.  Worrying that bits of github just die randomly, isn't
it?  https://status.github.com/ was itself down then, but according to
that now, the terms pages were only down for 3 minutes 0824-0827 PST
but I don't think 1904 or 2139 CEST are in that window... so I don't
think the status page is reliable and honest, even though it only
shows the last week.

> > Do they promise to not change the ToS in the future? Do they allow in the
> > ToS for signups with fake names or email addresses today? Not following
> > the site's terms to the letter can reduce leverage in the future if there
> > ever is a dispute.

github don't promise to not change the ToS.  github don't even promise
to tell users when the ToS change.  You have to keep checking and
playing "spot the difference".

github forbid signups with fake names or email addresses today.

> It is difficult or even impossible to make decision that everybody
> likes. But currently most developers are just fine with github.

I feel that more could have been done to make a decision that
everybody could live with.  Also, does that mean that there are some
current core developers who are not fine with github, too?

> And you can be sure that we will switch to a free solution if there
> is one available that is similar powerful than github.

There are tons of bug trackers and github is actually a pretty
simplistic one, so I don't think it's too hard to meet that.

> Migration will be easy because we can get everything out of github
> without problems.

OK, how could someone who wanted to get issues out of github do so?
I searched https://help.github.com/ for terms including "export
issues" and didn't find it.

The http://developer.github.com/v3/issues/ API doesn't look like it's
designed for migration, with its search only taking a single "since"
and not different ones for created_at, updated_at and closed_at - and
the API requires a github account anyway.

So it looks like migration can only be done by someone who has
accepted github - and by definition, they've less motive to help
migrate to something more open than those locked-out.

Confused,
-- 
MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op.
http://koha-community.org supporter, web and library systems developer.
In My Opinion Only: see http://mjr.towers.org.uk/email.html
Available for hire (including development) at http://www.software.coop/