From: "Wiles, Keith" <keith.wiles@intel.com>
To: Marc Sune <marc.sune@bisdn.de>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] GitHub sandbox for the DPDK community
Date: Tue, 5 May 2015 02:54:14 +0000 [thread overview]
Message-ID: <D16D7B95.1EB34%keith.wiles@intel.com> (raw)
In-Reply-To: <5547D7D5.2040508@bisdn.de>
On 5/4/15, 1:34 PM, "Marc Sune" <marc.sune@bisdn.de> wrote:
>
>
>On 01/05/15 20:17, Wiles, Keith wrote:
>>
>> On 5/1/15, 1:09 PM, "Stephen Hemminger" <stephen@networkplumber.org>
>>wrote:
>>
>>> On Fri, 1 May 2015 15:56:32 +0000
>>> "Wiles, Keith" <keith.wiles@intel.com> wrote:
>>>
>>>> Hi Everyone,
>>>>
>>>> I believe the DPDK community would benefit from moving to GitHub as
>>>>the
>>>> primary DPDK site. http://github.com
>>>>
>>>> I believe the DPDK community can benefit from being at a very well
>>>>know
>>>> world wide site. GitHub seems to have the most eyes of any of the open
>>>> source Git repos today and it appears they have more then twice as
>>>>many
>>>> developers. GitHub has a number of features I see as some good
>>>> additions to
>>>> our community using the GitHub organization account type.
>>>>
>>>> The cost for an organization account is $0 as long as we do not need
>>>> more
>>>> then 5 private repos.
>
>Minor issue:
>
>https://github.com/pricing
>
>Private repos for both users and organizations are not for free in
>github (they've never been afaik). They are in bitbucket, up to 5
>contributors.
Sorry, I could have sworn they gave 5 free, but you are correct we should
not require any private repos as we can use the teams and permissions.
Odd did they always have a cost for private repos for personal accounts? I
was thinking I had gotten 5 free in the beginning, but I have had to move
up to 10 repos a 8 months ago and I forget.
>
>But I don't get how private repositories have any influence in this
>discussion. Private repositories will be owned by companies and not DPDK
>as a community anyway.
>
>marc
>
>>>> 10 private repos is $25/month and had other plans
>>>> for more. I do not see us needing more then 5 private repos today and
>>>> the
>>>> only reason I can see having a private repo is to do some prep work on
>>>> the
>>>> repo before making public. Every contributor would need to create a
>>>> GitHub
>>>> personal account, which is at no cost unless you need more then 5
>>>> private
>>>> repos. In both accounts you can have unlimited public repos.
>>>>
>>>>
>>>>
>>>>https://help.github.com/articles/where-can-i-find-open-source-projects-
>>>>to
>>>> -w
>>>> ork-on/
>>>>
>>>> http://www.sitepoint.com/using-git-open-source-projects/
>>>>
>>>> - Adding more committers can lead to a security problems for 6Wind (I
>>>> assume).
>>>> - 6Wind appearing to own DPDK.org is not a good message to the
>>>> community.
>>>> - Not assuming 6Wind¹s dpdk.org site will disappear only where the
>>>> community stores the master repos and how the community interacts with
>>>> the
>>>> master.
>>>> - Permission and access levels in dpdk.org is only one level and we
>>>>can
>>>> benefit from having 4 levels and teams as well.
>>>> - The patch process today suffers from timely reviews, which will not
>>>>be
>>>> fixed by moving.
>>>> - GitHub has a per pull request discussions area, which gives a
>>>>clean
>>>> way to review all discussions on a specific change.
>>>> - The current patch model is clone/modify/commit/send patch set
>>>> - The model with GitHub is fork on GitHub/modify/commit/send pull
>>>> request
>>>> - The patchwork web site is reasonable, but has some draw backs in
>>>> maintaining the site.
>>>> - GitHub manages the patches via pull requests and can be easily
>>>>seen
>>>> via a web browser.
>>>> - The down side is you do have to use a web browser to do some work,
>>>> but
>>>> the bulk of the everyday work would be done as it is today.
>>>> - I think we all have a web browser now :-)
>>>> - GitHub has team support and gives a group better control plus
>>>> collaboration is much easier as we have a external location to work.
>>>> - Most companies have some pretty high security level and being to
>>>> collaborate between two or more companies is very difficult if one
>>>> company
>>>> is hosting the repo behind a firewall.
>>>> - Using GitHub and teams would make collaboration a lot easier or
>>>> collaboration between two or more user accounts as well.
>>>> - GitHub has a Web Page system, which can be customized for the
>>>> community
>>>> needs via a public or private repo.
>>>> - We still need a dpdk.org email list I believe as I did not find one
>>>>at
>>>> GitHub.
>>>> - We can also forward GitHub emails to the list.
>>>> - I believe you can reply to an email from GitHub and the email will
>>>> get
>>>> appended to the discussion thread.
>>>>
>>> In my experience the github pull model causes less review, not more.
>>> It only works if maintainers are motivated to do this as their full
>>>time
>>> job.
>>>
>>> With email, the patches are right in front of developers and easier to
>>> quote
>>> for review comments.
>> We are not getting the eyes on the review today, which means to me it
>>will
>> not matter if we move to GitHub method in the future.
Correct, we need to add a process to require reviews in some way, what
that process needs to be defined.
>>
>> Personally I am able to see the differences with the GitHub display and
>> helps me see what is really happening. The emails are too flat and then
>> they can indent forever or someones email client (like mine) screws up
>>the
>> format. With the GitHub method is will be exactly the same for everyone.
Moving to an easier reading display for everyone makes sense to me. Not
have to remember to add ―in-reply-to every time is also another reason to
adopt a system that handles this for you. Having a bunch of little
processes to manage is just asking for little mistakes and GitHub method
fixes this one.
Having everyone able to see the exact same style is the big plus that Marc
is pointing out here not what MUA someone uses.
>>
>
next prev parent reply other threads:[~2015-05-05 2:54 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 15:56 Wiles, Keith
2015-05-01 16:45 ` Neil Horman
2015-05-01 17:18 ` Aaro Koskinen
2015-05-04 12:39 ` Qiu, Michael
2015-05-01 17:31 ` Matthew Hall
2015-05-01 17:45 ` Wiles, Keith
2015-05-01 18:48 ` Neil Horman
2015-05-01 19:10 ` Wiles, Keith
2015-05-02 2:59 ` Wiles, Keith
2015-05-03 21:00 ` Neil Horman
2015-05-04 3:51 ` Wiles, Keith
2015-05-04 12:43 ` Qiu, Michael
2015-05-04 17:48 ` Matthew Hall
2015-05-04 18:52 ` Neil Horman
2015-05-05 3:12 ` Wiles, Keith
2015-05-05 3:25 ` Jim Thompson
2015-05-05 13:55 ` Neil Horman
2015-05-05 16:43 ` Wiles, Keith
2015-05-05 17:57 ` John W. Linville
2015-05-05 18:30 ` Wiles, Keith
2015-05-05 18:46 ` John W. Linville
2015-05-05 19:07 ` Neil Horman
2015-05-05 20:15 ` Wiles, Keith
2015-05-06 8:12 ` Panu Matilainen
2015-05-06 8:30 ` Simon Kågström
2015-05-06 9:00 ` Panu Matilainen
2015-05-06 10:37 ` Neil Horman
2015-05-07 15:26 ` John W. Linville
2015-05-01 18:01 ` Wiles, Keith
2015-05-01 18:09 ` Stephen Hemminger
2015-05-01 18:17 ` Wiles, Keith
2015-05-04 20:34 ` Marc Sune
2015-05-05 2:54 ` Wiles, Keith [this message]
2015-05-01 19:49 ` Matthew Hall
2015-05-01 19:59 ` Aaro Koskinen
2015-05-01 20:36 ` Matthew Hall
2015-05-02 11:40 ` Neil Horman
2015-05-02 12:37 ` Thomas F Herbert
2015-05-02 14:07 ` Wiles, Keith
2015-05-02 13:59 ` Wiles, Keith
2015-05-04 21:08 ` Marc Sune
2015-05-05 3:09 ` Wiles, Keith
2015-05-04 6:52 ` Simon
2015-05-04 9:05 ` Marc Sune
2015-05-06 10:11 ` Mcnamara, John
2015-05-06 21:09 ` Thomas Monjalon
2015-05-06 21:37 ` Marc Sune
2015-05-06 23:49 ` Wiles, Keith
2015-05-07 3:37 ` Wiles, Keith
2015-05-12 14:38 ` Thomas Monjalon
2015-05-04 5:08 Wiles, Keith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D16D7B95.1EB34%keith.wiles@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=marc.sune@bisdn.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).