From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] GitHub sandbox for the DPDK community
Date: Mon, 4 May 2015 05:08:29 +0000 [thread overview]
Message-ID: <D16C4CA7.1EA4B%keith.wiles@intel.com> (raw)
On 5/1/15, 10:56 AM, "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
Here is a good page showing the GitHub features:
https://github.com/features/
>
>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. 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.
>
>As most do not like to read long emails :-) I will stop here and add one
>more thing.
>
>I believe moving to GitHub for the DPDK community has a lot of advantages,
>but I also understand it will be different process and will cause a bit of
>issues as we convert. Having more eyes plus in a well know public location
>plus utilizing the extra features on Github plus a better public
>modifiable web pages is a few big advantages for the DPDK community.
>
>I have create a sandbox on GitHub for anyone to play with using GitHub.
>You will need to create a GitHub account and an email me your account name
>to add you to the organization site as a contributor.
>
>The GitHub site is not a fork of dpdk.org only a sandbox to play with how
>GitHub can help the community to gain more developers in a clean manner.
>
>https://github.com/dpdk-org
>
>
>Regards
>++Keith
>
>
>
>
>
>
next reply other threads:[~2015-05-04 5:08 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 5:08 Wiles, Keith [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=D16C4CA7.1EA4B%keith.wiles@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
/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).