What GitHub brings to the table are the review and collaboration tools. If you 
don’t need them, then you don’t need GitHub.

Kind regards,
Kirk

> On Jun 7, 2018, at 4:23 PM, Geertjan Wielenga 
> <geertjan.wiele...@googlemail.com> wrote:
> 
> We’re using GitHub as a convenience, thanks to GitBox. But there’s no
> requirement to use GitHub except that since it’s possible it’s popular
> because everyone knows GitHub. But we could use whatever Apache enables us
> to use.
> 
> Gj
> 
> On Thursday, June 7, 2018, Emilian Bold <emilian.b...@protonmail.ch> wrote:
> 
>> In theory. In practice we never saw a patch being discussed on the mailing
>> list.
>> 
>> Without GitHub you cannot comment on PRs, you cannot +1. You cannot create
>> a new PR.
>> 
>> --emi
>> 
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> 
>> On 7 June 2018 3:45 PM, Mark Struberg <strub...@yahoo.de.INVALID> wrote:
>> 
>>> To be honest I don't get why someone would require a github account.
>>> 
>>> Just clone our ASF git repo. Technically it makes no difference where
>> from. Might be from ASF, github or even your neighbour,..
>>> 
>>> The sha1 are everywhere the same anyway (if the clone is up2date).
>>> 
>>> Then you do your changes, create a patch etc. And send a pull request. I
>> personally even prefer creating the patch via git-format-patch and then
>> attaching it to either JIRA or send it directly to the mailing list for
>> review. That's how we always did work in the past and it still works like a
>> charm!
>>> 
>>> In many cases it's even way cleaner than via github (no spread channels
>> etc).
>>> 
>>> You could also just point to your repo (hosted on bitbucket,
>> sourceforge, your private server, whatever) and the maintainer could
>> git-fetch+merge from there. That's how GIT was intended to be used even.
>>> 
>>> LieGrue,
>>> 
>>> strub
>>> 
>>>> Am 07.06.2018 um 09:20 schrieb Jan Lahoda lah...@gmail.com:
>>>> 
>>>> Hi Emilian,
>>>> 
>>>> On Thu, Jun 7, 2018 at 8:33 AM, Emilian Bold
>> emilian.b...@protonmail.ch
>>>> 
>>>> wrote:
>>>> 
>>>>> I think we need to plan a separate contribution workflow without
>> GitHub
>>>>> 
>>>>> (see my other thread 'How to participate in Apache NetBeans without a
>>>>> 
>>>>> GitHub account?').
>>>>> 
>>>>> Right now we are tied to GitHub and it's impossible to be involved in
>>>>> 
>>>>> anything without jumping onto GitHub.
>>>> 
>>>> Not sure if (or why) it is impossible to be involved without GitHub.
>> AFAIK
>>>> 
>>>> anyone can subscribe to this mailing list, checkout from the Git repo
>> on
>>>> 
>>>> Apache:
>>>> 
>>>> https://gitbox.apache.org/repos/asf?p=incubator-netbeans.git
>>>> 
>>>> and send patches to this mailing list. (Or maybe links to patches, if
>> this
>>>> 
>>>> list strips attachments.)
>>>> 
>>>> My view is that we are using GitHub because it is more convenient.
>>>> 
>>>> Jan
>>>> 
>>>>> There is a high change of some contributors avoiding NetBeans if we
>> are
>>>>> 
>>>>> GitHub-only.
>>>>> 
>>>>> Demoting GitHub to a plain git remote is fine. We need to take care
>> of PRs
>>>>> 
>>>>> (code review / comments).
>>>>> 
>>>>> --emi
>>>>> 
>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>>> 
>>>>> On 7 June 2018 9:08 AM, Christian Lenz christian.l...@gmx.net wrote:
>>>>> 
>>>>>> Do any of you know the plans of MS? No, so please wait and don’t be
>>>>>> 
>>>>>> worry and make an Solutions, for Problems. That we Maybe not have.
>>>>>> 
>>>>>> Cheers
>>>>>> 
>>>>>> Chris
>>>>>> 
>>>>>> Von: Marc Beck
>>>>>> 
>>>>>> Gesendet: Mittwoch, 6. Juni 2018 21:10
>>>>>> 
>>>>>> An: dev@netbeans.incubator.apache.org
>>>>>> 
>>>>>> Betreff: Microsoft buys GitHub
>>>>>> 
>>>>>> Amen to that. Something I have been telling for so long.
>>>>>> 
>>>>>> In fact I can't remember a single thing M$ came up by themselves.
>> They
>>>>>> 
>>>>>> always bought stole, or equivalent. Even the initial CP-M is not
>>>>>> 
>>>>>> something
>>>>>> 
>>>>>> B.G. did come up with himself.
>>>>>> 
>>>>>> When people, around 2000 (XP) decided to stop writing anything that
>>>>>> 
>>>>>> could be
>>>>>> 
>>>>>> directly used by them it dried out. They got all the wizzes
>> together and
>>>>>> 
>>>>>> came up with a big flop (of which a very simplified run down
>> version we
>>>>>> 
>>>>>> know
>>>>>> 
>>>>>> under Vista).
>>>>>> 
>>>>>> Ergo why they bought GitHub: they are desperate for new material
>>>>>> 
>>>>>> Just my $.02
>>>>>> 
>>>>>> From: Chuck Davis [mailto:cjgun...@gmail.com]
>>>>>> 
>>>>>> Sent: Wednesday, June 06, 2018 1:20 PM
>>>>>> 
>>>>>> To: dev@netbeans.incubator.apache.org
>>>>>> 
>>>>>> Subject: Re: Microsoft buys GitHub
>>>>>> 
>>>>>> Do we need to be reminded that IBM had a 32 bit desktop OS a year
>> and a
>>>>>> 
>>>>>> half before MS could muster one up? They finally (20 years late)
>> gave
>>>>>> 
>>>>>> Windows 10 users two huge benefits millions of us have been
>> enjoying for
>>>>>> 
>>>>>> more that 20 years: virtual desktops (a VERY clumsy implementation
>> to be
>>>>>> 
>>>>>> sure) and a usable command prompt window.
>>>>>> 
>>>>>> Even at this time they are using their ridiculous "software
>> patents" to
>>>>>> 
>>>>>> prevent innovation and hold back the advance of the industry.
>>>>>> 
>>>>>> Microsoft is and always has been a poison to technology.
>> Everything they
>>>>>> 
>>>>>> have has been acquired either through purchasing or bankrupting the
>>>>>> 
>>>>>> innovator.
>>>>>> 
>>>>>> There's a lot of stuff on GitHub MS can now steal and market like
>> they
>>>>>> 
>>>>>> invented it...welcome to the Windows World. They've never invented
>>>>>> 
>>>>>> anything but they sure know how to market other people's
>> innovations.
>>>>>> 
>>>>>> The sooner NB liberates itself from GitHub the better off we'll
>> be. If
>>>>>> 
>>>>>> Git
>>>>>> 
>>>>>> is the tool of choice I say let Apache set up it's own Git
>> repositories
>>>>>> 
>>>>>> for
>>>>>> 
>>>>>> Apache projects.
>>>>>> 
>>>>>> On Wed, Jun 6, 2018 at 12:46 AM, Tim Boudreau niftin...@gmail.com
>> wrote:
>>>>>> 
>>>>>> Honestly, when I think of Microsoft, I think of the immeasurable
>> harm
>>>>>> 
>>>>>> they
>>>>>> 
>>>>>>> did to progress in computing. There was going to be a PC on every
>>>>>>> 
>>>>>>> desktop
>>>>>> 
>>>>>>> regardless. They just ensured that PC ran a horrifically flawed,
>>>>>>> 
>>>>>>> vulnerable, broken by design OS.
>>>>>> 
>>>>>> --
>>>>>> 
>>>>>> To unsubscribe, e-mail:
>> dev-unsubscr...@netbeans.incubator.apache.org
>>>>>> 
>>>>>> For additional commands, e-mail:
>> dev-h...@netbeans.incubator.apache.org
>>>>>> 
>>>>>> For further information about the NetBeans mailing lists, visit:
>>>>>> 
>>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>> 
>>>>> To unsubscribe, e-mail:
>> dev-unsubscr...@netbeans.incubator.apache.org
>>>>> 
>>>>> For additional commands, e-mail:
>> dev-h...@netbeans.incubator.apache.org
>>>>> 
>>>>> For further information about the NetBeans mailing lists, visit:
>>>>> 
>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>> 
>>> --
>>> 
>>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>>> 
>>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>>> 
>>> For further information about the NetBeans mailing lists, visit:
>>> 
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>> 
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>> 
>> 
>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Reply via email to