devel

devel@lists.centos.org

2 participants
4620 discussions

Resources Needed for Doc Toolchain Project [GSoC]
by kunaal jain 05 Jun '15

05 Jun '15

Hi, As discussed earlier about the workflow, I and Lei will need a server space to host Bugzilla, a test repository at Github + a git repository at git.centos.org. This is temporary, required for development and testing. Please let us know how do we obtain the same? We need it to get started on our project. Thanks! Regards, Kunaal

6 12

Re: [CentOS-devel] Regarding GSoC project : Documentation Toolchain
by Lei Yang 05 Jun '15

05 Jun '15

> On Sat, May 30, 2015 at 1:04 AM, kunaal jain <kunaalus at gmail.com <http://lists.centos.org/mailman/listinfo/centos-devel>> wrote: > > The typical workflow might look like this: > > > > 1. Author writes content in markdown language. > > 2. Makes a pull request on github. > > Is this github.com or, a git instance off CentOS infrastructure? Authors are supposed to make a pull request on github. > > > 3. Corresponding to the pull request a issue is created on bugzilla. > > 4. CentOS staff can either review the article on github pull request, or on > > bugzilla. > > I would recommend using one tool for handle inbound and review. Having > 2 tools that need to be kept synchronized would add overhead that you > don't want to deal with. Also, it has the effect of puzzling > contributors. Thanks for your suggestion! Staff will do the review only on bugzilla, but we think some contributors are only familiar with github, so we sync the comments between two platforms, so contributors don’t need to leave github to finish the whole process. > > > 5. Comments are two way synced. > > 6. At each point the article can be viewed on bugzilla, using an extension > > we propose to make. > > 7. After many iterations of commenting, and improving, article is finally > > accepted. > > Have you considered review workflow tools like Gerrit? We considered Gerrit and other code review platforms. However we are handling markdown or some similar markup languages, so we plan to build the doc on a CI and let the staff review the built docs. > > > 8. Staff tags it, and pushes to git.centos.org. > > 9. Using git.centos.org, new website is generated and pushed. > > 'Website' or, is the content rendered from the version control (g.c.o) > and pushed live? The content is rendered from g.c.o. built into HTML files using static site generator tool like jekyll. Regards, Lei

2 4

Meeting log from this week's cloud sig meeting
by Kushal Das 05 Jun '15

05 Jun '15

=============================== #centos-devel: CentOS Cloud SIG =============================== Meeting started by kushal at 15:00:32 UTC. The full logs are available at http://centos.org/minutes/2015/may/centos-devel.2015-05-28-15.00.log.html . Meeting summary --------------- * Roll Call (kushal, 15:00:39) * tmrts is developing a cloud instance contextualization tool as a GSoC project (kushal, 15:04:45) * ACTION: tmrts will put up the roadmap to a github repo and share the link in the centos-devel list. (kushal, 15:06:57) * tmrts's project will focus on CentOS Atomic Host. (kushal, 15:08:01) * Update from OpenNebula (kushal, 15:09:52) * jmelis is studying about CBS. (kushal, 15:11:39) * jmelis is developing a set of tests to test the CBS based installs. (kushal, 15:12:43) * LINK: http://meetbot.debian.net/Manual.html (kushal, 15:14:27) * Openstack updates (kushal, 15:15:21) * Open Floor (kushal, 15:22:41) * LINK: http://community.redhat.com/blog/2015/05/highlights-from-rdo-meeting-at-ope… (kushal, 15:24:29) * LINK: https://review.openstack.org/#/c/185187/ (number80, 15:26:06) * planning a RDO track at FOSDEM CentOS dojo (number80, 15:29:18) Meeting ended at 15:35:26 UTC. Action Items ------------ * tmrts will put up the roadmap to a github repo and share the link in the centos-devel list. Action Items, by person ----------------------- * tmrts * tmrts will put up the roadmap to a github repo and share the link in the centos-devel list. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * kushal (62) * rbowen (30) * number80 (26) * jmelis (11) * tmrts (10) * Arrfab (5) * alphacc (3) * centbot (3) * Evolution (3) * hughesjr (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Kushal Das -- Fedora Cloud Engineer CPython Core Developer Director @ Python Software Foundation http://kushaldas.in

2 1

Re: [CentOS-devel] Where to GSoC blog?
by Lei Yang 05 Jun '15

05 Jun '15

Hi, I think writing on a central place like seven.centos.org <http://seven.centos.org/> is a great choice. I’ve written some blog articles in Chinese, and I am willing to write them in English and post on seven.centos.org <http://seven.centos.org/> :) Regards, Lei

1 0

Regarding GSoC project : Documentation Toolchain
by kunaal jain 05 Jun '15

05 Jun '15

Hi, Over the last week, Lei and I have been researching about the review platform where the content submitted can be reviewed, commented, tagged and pushed. This will be an alternative to github pull requests interface, which will thus reduce our dependency on Github in case Github changes its API anytime in future. Even firefox is considering using Github as an alternative medium to receive contribution. http://gregoryszorc.com/blog/2015/01/12/utilizing-github-for-firefox-develo… Lei made a great chart comparing the platforms. https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=shari… So overall Bugzilla looks a great option. But there is one major flaw, we need to view the article submitted at each point(code review) which bugzilla lacks. The solution to this is creating a plugin for markdown previewing. The typical workflow might look like this: 1. Author writes content in markdown language. 2. Makes a pull request on github. 3. Corresponding to the pull request a issue is created on bugzilla. 4. CentOS staff can either review the article on github pull request, or on bugzilla. 5. Comments are two way synced. 6. At each point the article can be viewed on bugzilla, using an extension we propose to make. 7. After many iterations of commenting, and improving, article is finally accepted. 8. Staff tags it, and pushes to git.centos.org. 9. Using git.centos.org, new website is generated and pushed. There are many challenging tasks in this, especially the bugzilla issue creation on pull request and two way comment sync. This has never been done before, but we looked at the API and think we can make it work. Another challenging task is markdown preview on bugzilla. Please let us know, what you think about this? Regards, Kunaal -- Regards, Kunaal Jain

2 1

Cloud SIG meeting minutes (2015-06-04)
by Rich Bowen 05 Jun '15

05 Jun '15

Thanks to those that attended the Cloud SIG Meeting. Minutes follow. Minutes may also be found online at: http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.txt http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.html Full logs may be found at: http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.log.html http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.log.txt ===================== #centos-devel Meeting ===================== Meeting started by rbowen at 15:00:53 UTC. The full logs are available at centos-devel/2015/centos-devel.2015-06-04-15.00.log.html . Meeting summary --------------- * LINK: https://etherpad.openstack.org/p/cloud_sig_agenda (rbowen, 15:01:05) * rollcall (rbowen, 15:01:16) * Update on Juno/Kilo releases (rbowen, 15:04:19) * GSOC updates (rbowen, 15:06:03) * My project is related to atomic, fedora and centOS (tmrts, 15:07:43) * LINK: https://github.com/TamerTas/cloud-init/blob/master/ROADMAP.md (tmrts, 15:08:38) * First few weeks I'll be focusing on the core part of the cloud-init (users, network, ssh, custom scripts) then I'll get to the specifics of each target system (tmrts, 15:09:37) * Open Floor (rbowen, 15:17:22) * ACTION: I'll add CentOS 6 to the cloud-init test environment (tmrts, 15:22:26) Meeting ended at 15:28:31 UTC. Action Items ------------ * I'll add CentOS 6 to the cloud-init test environment Action Items, by person ----------------------- * **UNASSIGNED** * I'll add CentOS 6 to the cloud-init test environment People Present (lines said) --------------------------- * rbowen (33) * kbsingh (19) * tmrts (17) * apevec (6) * centbot (2) * number80 (2) * alphacc (1) * Evolution (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

1 0

moving ci.dev
by Karanbir Singh 05 Jun '15

05 Jun '15

hi guys, I believe we are fairly well established on the ci.centos.org infra to now consider moving the ci.dev instances from their present location at godaddy.com. This would also allow us to run the ci.dev nightly tests on baremetal machines. It would also allow us to consolidate the jenkins instance, and maybe SIGs and other tested projects could use the distro runs as a trigger for their own validation / testing. Brian, can we find a slot in one of the CBS meetings to work through this ? Regards, -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

4 4

Image builds in cbs.centos.org
by Karanbir Singh 05 Jun '15

05 Jun '15

hi, Why do the image builds in cbs/koji take so long ( upto 45 minutes ) when the same kickstart run with virt-install will finish in ~ 3 min, and the qemu-img converts take a few minutes as well. On similar spec hardware as the koji builders themselves. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Where to GSoC blog?
by Karsten Wade 04 Jun '15

04 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 One of the tasks of the GSoC students is to write up their work and experiences as they go, typically with at least one blog post per week. Often projects then put the students on the main project planet or a special GSoC-specific planet. KB had the idea that instead we might want students and mentors to use e.g. seven.centos.org to blog from instead. I've asked around and can't be sure how project planets get used. Some people read them, many don't. Individual blogs get picked up in e.g. Google, so that's one reason for using seven.centos.org -- to improve searching around the GSoC topics. Thoughts? We're a bit in to the process, I should have pushed on a decision sooner, so I appreciate any quick feedback. Thanks - Karsten - -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVwnyIACgkQ2ZIOBq0ODEEwRQCg2hbch9DkVjoJEL6NKTa8tu6I gmsAoMsQjTAqZep1z2IhT8S928YLVsds =wSd/ -----END PGP SIGNATURE-----

2 1

CentOS SCLo SIG sync-up meeting on #centos-devel next week
by Honza Horak 03 Jun '15

03 Jun '15

Sorry for late announcement, but I'm not able to hold today's meeting, let's try the next week. However, if there are some updates since last meeting two weeks back about look-aside cache or koji tags stuff, give us know, please. Adam, Brian, have you got in touch somehow? Honza

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel