Hi All,

I did a test project for migrating to Sourceforge.  I copied over the
git repo and used a modified version of sf2github.  The result is at:

https://github.com/csound/csound-migration-test

Issues were a little tricky; I mapped them as best as I could. To
note, each tracker on Sourecforge gets exported as an individual json
file, so importing those to Github has the "SF #xxx" numbered per
tracker, i.e. there may be multiple SF #1's there.

Anyways, comments very welcome!

steven

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Thu, Feb 20, 2014 at 12:37 AM, Steven Yi  wrote:
> Hi All,
>
> I did a test project for migrating to Sourceforge.  I copied over the
> git repo and used a modified version of sf2github.  The result is at:
>
> https://github.com/csound/csound-migration-test
>
> Issues were a little tricky; I mapped them as best as I could. To
> note, each tracker on Sourecforge gets exported as an individual json
> file, so importing those to Github has the "SF #xxx" numbered per
> tracker, i.e. there may be multiple SF #1's there.
>
> Anyways, comments very welcome!

A notice few things:

The milestones do not get imported. The bugs have a note saying
milestone: csound6 but ther is no milestone with that name.

Same as the priority. Github doesn't appear to have a priority system,
but what I've done on a few private projects is to tag them with
priority- (I would suggest using high - low - medium instead of
numbers).

The git repo points to master by default. The github admin page has a
section where you can change HEAD to point to develop instead.

All issues are reported and commented by you, which makes it hard to
read (eg, issue 514). I assume the github API doen't allow you to post
messages as other people, but perhaps the script can be modified to
print the name if the sender in the message? Sort of like an email
reply: "Felipe Sateler said: "

Finally, maybe it could be useful to tag each issue with the name of
the tracker it came from. So issues could be tagged
"platform-specific" or "build-system". Is that feasible?

Otherwise it looks good to me!



-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Do we need to migrate all tickets or only the open ones?
Also would we need to migrate the ones referring to Csound 5?

Victor

On 20 Feb 2014, at 13:11, Felipe Sateler  wrote:

> On Thu, Feb 20, 2014 at 12:37 AM, Steven Yi  wrote:
>> Hi All,
>> 
>> I did a test project for migrating to Sourceforge.  I copied over the
>> git repo and used a modified version of sf2github.  The result is at:
>> 
>> https://github.com/csound/csound-migration-test
>> 
>> Issues were a little tricky; I mapped them as best as I could. To
>> note, each tracker on Sourecforge gets exported as an individual json
>> file, so importing those to Github has the "SF #xxx" numbered per
>> tracker, i.e. there may be multiple SF #1's there.
>> 
>> Anyways, comments very welcome!
> 
> A notice few things:
> 
> The milestones do not get imported. The bugs have a note saying
> milestone: csound6 but ther is no milestone with that name.
> 
> Same as the priority. Github doesn't appear to have a priority system,
> but what I've done on a few private projects is to tag them with
> priority- (I would suggest using high - low - medium instead of
> numbers).
> 
> The git repo points to master by default. The github admin page has a
> section where you can change HEAD to point to develop instead.
> 
> All issues are reported and commented by you, which makes it hard to
> read (eg, issue 514). I assume the github API doen't allow you to post
> messages as other people, but perhaps the script can be modified to
> print the name if the sender in the message? Sort of like an email
> reply: "Felipe Sateler said: "
> 
> Finally, maybe it could be useful to tag each issue with the name of
> the tracker it came from. So issues could be tagged
> "platform-specific" or "build-system". Is that feasible?
> 
> Otherwise it looks good to me!
> 
> 
> 
> -- 
> 
> Saludos,
> Felipe Sateler
> 
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Felipe,

I just got around to looking at this again.  I've modified the script,
closed out the original imports, and re-imported all of the tickets.
I'll reply in-line below, thanks!

steven


> A notice few things:
>
> The milestones do not get imported. The bugs have a note saying
> milestone: csound6 but ther is no milestone with that name.

I think the milestones are alright.  I do notice there are some
milestones that are marked as "closed" that can just be reopened.  If
you see one that has a milestone that isn't there, let me know which
it is so I can look into it.  (I don't think the GH API would allow
adding tickets to a milestone that isn't already in the system).

> Same as the priority. Github doesn't appear to have a priority system,
> but what I've done on a few private projects is to tag them with
> priority- (I would suggest using high - low - medium instead of
> numbers).

I skipped this as I didn't think priority was worthwhile to use and I
thought it might pollute the labels.  I think just using what is
assigned to whom, plus if we start using the milestone system to
assign tickets to milestones, we'll have enough visibility on issues.

> The git repo points to master by default. The github admin page has a
> section where you can change HEAD to point to develop instead.

Done.

> All issues are reported and commented by you, which makes it hard to
> read (eg, issue 514). I assume the github API doen't allow you to post
> messages as other people, but perhaps the script can be modified to
> print the name if the sender in the message? Sort of like an email
> reply: "Felipe Sateler said: "

Yes, it's how the API works and it makes sense to prevent creating
tickets as other users.  I've modified the scripts to add some bold
text on who reported the issue and who commented on them. Could you
take a look and see if it is satisfactory?

> Finally, maybe it could be useful to tag each issue with the name of
> the tracker it came from. So issues could be tagged
> "platform-specific" or "build-system". Is that feasible?

I've modified the part where it says [sf #xxx] to be [sf trackerName #xxx].

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Victor,

My thoughts are that it's worth having a record of the older tickets
in case someone wants to lookup some background info.  As for
migrating tickets referring to CS5, I think it's fine to migrate the
ticket and we can choose to close it out.  It's simpler at this point
IMO to do that than to try to filter for CS5 related tickets.

Thanks!
steven

On Thu, Feb 20, 2014 at 8:27 AM, Victor Lazzarini
 wrote:
> Do we need to migrate all tickets or only the open ones?
> Also would we need to migrate the ones referring to Csound 5?
>
> Victor
>
> On 20 Feb 2014, at 13:11, Felipe Sateler  wrote:
>
>> On Thu, Feb 20, 2014 at 12:37 AM, Steven Yi  wrote:
>>> Hi All,
>>>
>>> I did a test project for migrating to Sourceforge.  I copied over the
>>> git repo and used a modified version of sf2github.  The result is at:
>>>
>>> https://github.com/csound/csound-migration-test
>>>
>>> Issues were a little tricky; I mapped them as best as I could. To
>>> note, each tracker on Sourecforge gets exported as an individual json
>>> file, so importing those to Github has the "SF #xxx" numbered per
>>> tracker, i.e. there may be multiple SF #1's there.
>>>
>>> Anyways, comments very welcome!
>>
>> A notice few things:
>>
>> The milestones do not get imported. The bugs have a note saying
>> milestone: csound6 but ther is no milestone with that name.
>>
>> Same as the priority. Github doesn't appear to have a priority system,
>> but what I've done on a few private projects is to tag them with
>> priority- (I would suggest using high - low - medium instead of
>> numbers).
>>
>> The git repo points to master by default. The github admin page has a
>> section where you can change HEAD to point to develop instead.
>>
>> All issues are reported and commented by you, which makes it hard to
>> read (eg, issue 514). I assume the github API doen't allow you to post
>> messages as other people, but perhaps the script can be modified to
>> print the name if the sender in the message? Sort of like an email
>> reply: "Felipe Sateler said: "
>>
>> Finally, maybe it could be useful to tag each issue with the name of
>> the tracker it came from. So issues could be tagged
>> "platform-specific" or "build-system". Is that feasible?
>>
>> Otherwise it looks good to me!
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
>>
>> ------------------------------------------------------------------------------
>> Managing the Performance of Cloud-Based Applications
>> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
>> Read the Whitepaper.
>> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thank you very much for doing this. 



--
View this message in context: http://csound.1045644.n5.nabble.com/Github-Migration-Test-tp5732688p5732794.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Mon, Feb 24, 2014 at 6:30 PM, Steven Yi  wrote:
> Hi Felipe,
>
> I just got around to looking at this again.  I've modified the script,
> closed out the original imports, and re-imported all of the tickets.
> I'll reply in-line below, thanks!
>
> steven
>
>
>> A notice few things:
>>
>> The milestones do not get imported. The bugs have a note saying
>> milestone: csound6 but ther is no milestone with that name.
>
> I think the milestones are alright.  I do notice there are some
> milestones that are marked as "closed" that can just be reopened.  If
> you see one that has a milestone that isn't there, let me know which
> it is so I can look into it.  (I don't think the GH API would allow
> adding tickets to a milestone that isn't already in the system).

OK now I see them. I was confused because not all milestones appear to
show where I was looking (In the no milestone selected popup in the
issues page).

>
>> Same as the priority. Github doesn't appear to have a priority system,
>> but what I've done on a few private projects is to tag them with
>> priority- (I would suggest using high - low - medium instead of
>> numbers).
>
> I skipped this as I didn't think priority was worthwhile to use and I
> thought it might pollute the labels.  I think just using what is
> assigned to whom, plus if we start using the milestone system to
> assign tickets to milestones, we'll have enough visibility on issues.

OK.

>
>> The git repo points to master by default. The github admin page has a
>> section where you can change HEAD to point to develop instead.
>
> Done.

Great!

>
>> All issues are reported and commented by you, which makes it hard to
>> read (eg, issue 514). I assume the github API doen't allow you to post
>> messages as other people, but perhaps the script can be modified to
>> print the name if the sender in the message? Sort of like an email
>> reply: "Felipe Sateler said: "
>
> Yes, it's how the API works and it makes sense to prevent creating
> tickets as other users.  I've modified the scripts to add some bold
> text on who reported the issue and who commented on them. Could you
> take a look and see if it is satisfactory?

Yes, looks much better. It is now possible to follow along now.

>
>> Finally, maybe it could be useful to tag each issue with the name of
>> the tracker it came from. So issues could be tagged
>> "platform-specific" or "build-system". Is that feasible?
>
> I've modified the part where it says [sf #xxx] to be [sf trackerName #xxx].

The point of tags is that it is easier to filter. But if it works for
you, then I'm OK with it.


Its looking good!

-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net