Enabling GitHub "Issues" and "Wiki" for flex repositories

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Enabling GitHub "Issues" and "Wiki" for flex repositories

Olaf Krueger
Hi,
I would like to create an INFRA Jira in order to ask them to enable GitHub
"Issues" and the "Wiki" for following repositories:

 - flex-tlf.git
 - flex-utilities.git
 - flex-flexunit.git
 - flex-site.git
 - flex-external.git
 - flex-sdk.git
 - flex-blazeds.git
 - flex-radii8.git

We will maybe use these GitHub features mainly for the flex-sdk repo, but
maybe it makes sense to just enable it for all flex repos?

Any objections?

Thanks,
Olaf




--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Carlos Rovira-3
That's ok for me, thanks! :)

About the old flex wiki, I think we still have some good info about FlexJS
still not migrated to Royale. I assume all this migration is not about all
of that right?

thanks!



El mar., 8 ene. 2019 a las 10:10, Olaf Krueger (<[hidden email]>)
escribió:

> Hi,
> I would like to create an INFRA Jira in order to ask them to enable GitHub
> "Issues" and the "Wiki" for following repositories:
>
>  - flex-tlf.git
>  - flex-utilities.git
>  - flex-flexunit.git
>  - flex-site.git
>  - flex-external.git
>  - flex-sdk.git
>  - flex-blazeds.git
>  - flex-radii8.git
>
> We will maybe use these GitHub features mainly for the flex-sdk repo, but
> maybe it makes sense to just enable it for all flex repos?
>
> Any objections?
>
> Thanks,
> Olaf
>
>
>
>
> --
> Sent from: http://apache-flex-development.2333347.n4.nabble.com/
>


--
Carlos Rovira
http://about.me/carlosrovira
Reply | Threaded
Open this post in threaded view
|

Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Alex Harui-2
I'm not opposed, but I'm not sure it is worth it.  I think there are a 800+ bugs filed since Flex came to Apache that are still open in JIRA so JIRA is known to our Flex users.  Not sure if it will be confusing to have two places to look and I don't think we should migrate those bugs either.  Same for the wiki.  There's good content there but that content may not be worth migrating.  But if someone wants to take the time, update the website links, etc, that's fine with me.

My 2 cents,
-Alex

On 1/8/19, 8:41 AM, "Carlos Rovira" <[hidden email]> wrote:

    That's ok for me, thanks! :)
   
    About the old flex wiki, I think we still have some good info about FlexJS
    still not migrated to Royale. I assume all this migration is not about all
    of that right?
   
    thanks!
   
   
   
    El mar., 8 ene. 2019 a las 10:10, Olaf Krueger (<[hidden email]>)
    escribió:
   
    > Hi,
    > I would like to create an INFRA Jira in order to ask them to enable GitHub
    > "Issues" and the "Wiki" for following repositories:
    >
    >  - flex-tlf.git
    >  - flex-utilities.git
    >  - flex-flexunit.git
    >  - flex-site.git
    >  - flex-external.git
    >  - flex-sdk.git
    >  - flex-blazeds.git
    >  - flex-radii8.git
    >
    > We will maybe use these GitHub features mainly for the flex-sdk repo, but
    > maybe it makes sense to just enable it for all flex repos?
    >
    > Any objections?
    >
    > Thanks,
    > Olaf
    >
    >
    >
    >
    > --
    > Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.2333347.n4.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C082657ca2436418529cb08d675882ff3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636825625117173639&amp;sdata=FmviyLt3BGx3m7ysRUtjEMLfoUIGF35D%2F78xbhgsfz4%3D&amp;reserved=0
    >
   
   
    --
    Carlos Rovira
    https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C082657ca2436418529cb08d675882ff3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636825625117173639&amp;sdata=Y2RMBHeYo3aP52ueG26cd805XInmz5V4Q8kGfOVdQ1I%3D&amp;reserved=0
   

Reply | Threaded
Open this post in threaded view
|

Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Olaf Krueger
I was thinking more like a cut of the old Wiki and JIRA than a migration of
the existing stuff.
I think it would be easier and more transparent for folks to handle future
development (if it will happen) by using GitHub.
We may migrate some wiki stuff someday, don't know.

Thanks,
Olaf





--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Alex Harui-2
Are we going to say that we won't fix any of the bugs currently open in JIRA?  That might be ok.  It would help prioritize and make more clear what folks are still interested in.  My concern is having two active bug bases.  You may still end up referencing the JIRA bugs when marking new bugs as duplicates.

-Alex

On 1/8/19, 11:37 AM, "Olaf Krueger" <[hidden email]> wrote:

    I was thinking more like a cut of the old Wiki and JIRA than a migration of
    the existing stuff.
    I think it would be easier and more transparent for folks to handle future
    development (if it will happen) by using GitHub.
    We may migrate some wiki stuff someday, don't know.
   
    Thanks,
    Olaf
   
   
   
   
   
    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.2333347.n4.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C134f454fbec74f08d97a08d675a0bada%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636825730552562081&amp;sdata=GF7m81Kmna%2BISLtw2z1wsCKXyoTO4ps151zPAu2E9D0%3D&amp;reserved=0
   

Reply | Threaded
Open this post in threaded view
|

Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Justin Mclean
Administrator
In reply to this post by Olaf Krueger
Hi,

> I think it would be easier and more transparent for folks to handle future development (if it will happen) by using GitHub.

i’m that sure that it is. JIRA has a number of significant benefits over GitHub issues including better searching and querying. (Yes I use both).

Do we know if it possible it import all historical JIRA issues (open and closed) into git issues? And if we do what if anything do we loose? Don’t forget the old Adobe issues are also in JIRA and having a history of which bugs have been resolved or not is very useful.

Thanks,
Justin
Reply | Threaded
Open this post in threaded view
|

Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Olaf Krueger
> Do we know if it possible it import all historical JIRA issues ...

I don't know it this is possible.

> JIRA has a number of significant benefits over GitHub issues including
> better searching and querying

JIRA is probably more powerful but I guess the simplicity of GitHub is the
greater advantage here.

I think if we would go with GitHub issues it would be a good opportunity for
a "clean restart".
That doesn't mean that the existing JIRA issues are useless, these should
remain there.

Olaf






--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Olaf Krueger
In reply to this post by Alex Harui-2
> Are we going to say that we won't fix any of the bugs currently open in
JIRA?...
> My concern is having two active bug bases...

We maybe could set or treat or freeze JIRA as read-only and could link to
the entire Flex-JIRA from GitHub in order to not losing the history.
If somebody is going to fix one of those existing JIRA issues we could
simply recreate it manually as a GitHub issue.
If somebody will file a new GitHub issue we may want to check if there's a
JIRA duplicate in order to link it from the GitHub issue.
But on the other hand, I don't believe when somebody creates a new JIRA that
somebody checks if there's already a JIRA duplicate.

Thoughts?

Olaf



--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Carlos Rovira-3
Hi Olaf,

I like your idea. I think going to GitHub is like when we migrate from SVN
to GIT, we must go with the times.
Is like FlexJS vs Royale wiki. We started a new one with newer info in
Royale, but still have useful content from FlexJS that we should not remove
and migrate as we can.

So for me is ok to star clean on Github and lock JIRA, (or just be able to
close or update JIRA content, but be unable to create new ones on JIRA.
People working in Flex should now that as part of the things they need to
know. If want to create a new ticket, first check JIRA, but create from
scratch or recreate in Github. This will be an improvement for Flex in the
end

just my 2...

Carlos




El mar., 8 ene. 2019 a las 23:18, Olaf Krueger (<[hidden email]>)
escribió:

> > Are we going to say that we won't fix any of the bugs currently open in
> JIRA?...
> > My concern is having two active bug bases...
>
> We maybe could set or treat or freeze JIRA as read-only and could link to
> the entire Flex-JIRA from GitHub in order to not losing the history.
> If somebody is going to fix one of those existing JIRA issues we could
> simply recreate it manually as a GitHub issue.
> If somebody will file a new GitHub issue we may want to check if there's a
> JIRA duplicate in order to link it from the GitHub issue.
> But on the other hand, I don't believe when somebody creates a new JIRA
> that
> somebody checks if there's already a JIRA duplicate.
>
> Thoughts?
>
> Olaf
>
>
>
> --
> Sent from: http://apache-flex-development.2333347.n4.nabble.com/
>


--
Carlos Rovira
http://about.me/carlosrovira
Reply | Threaded
Open this post in threaded view
|

RE: [Non-DoD Source] Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Kessler CTR Mark J-2
+1

Especially those old Adobe issues that were imported.  To me they are mostly clutter because of the quantity, age, and missing attachments.  I would much rather have a clean start.  But brining in any new (from a given time range x number of months) wouldn't be a bonus, unless that's an entirely manual process.

-Mark K


-----Original Message-----
From: Carlos Rovira [mailto:[hidden email]]
Sent: Wednesday, January 9, 2019 4:32 AM
To: [hidden email]
Subject: [Non-DoD Source] Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Hi Olaf,

I like your idea. I think going to GitHub is like when we migrate from SVN
to GIT, we must go with the times.
Is like FlexJS vs Royale wiki. We started a new one with newer info in
Royale, but still have useful content from FlexJS that we should not remove
and migrate as we can.

So for me is ok to star clean on Github and lock JIRA, (or just be able to
close or update JIRA content, but be unable to create new ones on JIRA.
People working in Flex should now that as part of the things they need to
know. If want to create a new ticket, first check JIRA, but create from
scratch or recreate in Github. This will be an improvement for Flex in the
end

just my 2...

Carlos




El mar., 8 ene. 2019 a las 23:18, Olaf Krueger (<[hidden email]>)
escribió:

> > Are we going to say that we won't fix any of the bugs currently open in
> JIRA?...
> > My concern is having two active bug bases...
>
> We maybe could set or treat or freeze JIRA as read-only and could link to
> the entire Flex-JIRA from GitHub in order to not losing the history.
> If somebody is going to fix one of those existing JIRA issues we could
> simply recreate it manually as a GitHub issue.
> If somebody will file a new GitHub issue we may want to check if there's a
> JIRA duplicate in order to link it from the GitHub issue.
> But on the other hand, I don't believe when somebody creates a new JIRA
> that
> somebody checks if there's already a JIRA duplicate.
>
> Thoughts?
>
> Olaf
>
>
>
> --
> Sent from: http://apache-flex-development.2333347.n4.nabble.com/
>


--
Carlos Rovira
http://about.me/carlosrovira
Reply | Threaded
Open this post in threaded view
|

Re: Enabling GitHub "Issues" and "Wiki" for flex repositories

Olaf Krueger
In reply to this post by Justin Mclean
@Justin

> i’m that sure that it is. JIRA has a number of significant benefits over
> GitHub issues including better searching and querying. (Yes I use both).

Just to make sure that I got it right:
Does that mean that you basically support the idea of moving from JIRA to
GitHub issues or do you see some significant drawbacks?

@All
In order to get an "official" result, I propose to start a vote about it.
Will do this soon...

Thanks,
Olaf





--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/