Issue tickets transferred from Googlecode to GitHub

[Graham Higgins]

Dear all,

I managed to transfer to Github the entire issue ticket logs for both RDFLib and rdfextras. 

Some degree of compromise proved necessary - I was not able to replicate the original posters' and commenters' ids, so I bolted the comments on to the end of the original ticket.

Github issue categories are quite free-form, I created some broad categories, largely aimed at informing both observers and participants about the range and state of affairs and attempting to make it clear what issues are being worked on currently and by whom (the latter inferred from statements made in the corresponding posting/comments), what issues are in the process of being thrashed out in discussion and whether the issue relates to a bug or a proposed enhancement or is a documentation-related issue.

That's about it for the migration, thank you all for your co-operation.

Cheers,

Graham.

[Gunnar Aastrand Grimnes]

Thanks again for the probably quite tediuous migration work Graham!

Just a quick pointer - github supports (like google code did) closing
and refering to tickets from commit messages, see here:
https://github.com/blog/831-issues-2-0-the-next-generation

i.e. this means that if you commit something and do "fixes #123" this
will close issue 123 and the change will have nice links etc. when
viewed on github.com

Cheers,

- Gunnar

> --
> You received this message because you are subscribed to the Google Groups
> "rdflib-dev" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/rdflib-dev/-/X_QnaYpMzU4J.
> To post to this group, send email to rdfli...@googlegroups.com.
> To unsubscribe from this group, send email to
> rdflib-dev+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rdflib-dev?hl=en.

--
http://gromgull.net

[Graham Higgins]

On Tuesday, 21 February 2012 13:12:31 UTC, Gunnar Aastrand Grimnes wrote:

... probably quite tedious migration work ...

Oh lor, GitHub wasn't sending out email was it? I /do/ hope not. 

If it was, please accept my apologies.

i.e. this means that if you commit something and do "fixes #123" this

will close issue 123 and the change will have nice links etc. when
viewed on github.com

Ah, /that's/ the convention, thanks.

 

My next task is to create a solution to the problem of routing 

commit notifications and issue posts to the googlegroup 

mailing list.

Cheers,

Graham

[Thomas Kluyver]

On 22 February 2012 01:12, Graham Higgins <gjhi...@gmail.com> wrote:
> Oh lor, GitHub wasn't sending out email was it? I /do/ hope not.
> If it was, please accept my apologies.

Yep, I wondered why I suddenly had 500 extra unread emails. ;-) It's
OK, though, it was pretty simple to select and file them all.

Thomas

[Graham Higgins]

On Wednesday, 22 February 2012 01:27:21 UTC, Thomas Kluyver wrote:

On 22 February 2012 01:12, Graham Higgins wrote:
> Oh lor, GitHub wasn't sending out email was it? I /do/ hope not.
> If it was, please accept my apologies.

Yep, I wondered why I suddenly had 500 extra unread emails. ;-)

<blush>

Sorry about that. A moment's inattention on my part and I fed a loop to a 

loop and I had to scramble about in ps wafx to kill it.

Dratted GitHub-flavoured markdown treats a single leading hash as an H1,

making code comments very LOUD :-) so I had to wrap the content in a 

<pre></pre> ... and then I saw that I had to retrieve the comments 

separately and bolt them on to the end of the original post ... and then 

I had to preface them with the poster's truncated email and the date ... 

and so on.

So yes, somewhat tedious.

Next time I'll know to create a separate sample set to work on.

Cheers,

Graham

[Graham Higgins]

On Wednesday, 22 February 2012 01:12:32 UTC, Graham Higgins wrote:

 

My next task is to create a solution to the problem of routing 

commit notifications and issue posts to the googlegroup 

mailing list.

Um, maybe people don't want this degree of detail. It'd also 

mean that github contributors would get notifications twice, 

once from GitHub and again via the mailing list.

What's the general preference for notifications published to the

mailing list / googlegroup?

a. changes and comments to issue tickets

b. commits

c. changes in CI build status

d. changes to the RTD documentation

or perhaps keep the mailing list clear of development 

administrivia and just publish the notifications as a set of 

RSS(atom) streams for people to subscribe to according

to preference?

Cheers,

Graham

[Gunnar Aastrand Grimnes]

>
>> ... probably quite tedious migration work ...
>
> Oh lor, GitHub wasn't sending out email was it? I /do/ hope not.
> If it was, please accept my apologies.

Actually I didn't get any - I just assumed it was tedious since you
had actually copied the comments etc!

Also - I've used rss2email to push tickets to mailinglists before:
http://www.allthingsrss.com/rss2email/
if you have a server with cron somewhere it works fine.

- Gunnar

--
http://gromgull.net

[Gunnar Aastrand Grimnes]

> Also - I've used rss2email to push tickets to mailinglists before:
> http://www.allthingsrss.com/rss2email/
> if you have a server with cron somewhere it works fine.

... but I cannot find an atom feed for issues on github? Did anyone else?