From silvertip257 at gmail.com Fri May 1 17:17:10 2015 From: silvertip257 at gmail.com (Mike - st257) Date: Fri, 1 May 2015 13:17:10 -0400 Subject: [CentOS-docs] delete account In-Reply-To: References: Message-ID: On Thu, Apr 30, 2015 at 12:31 PM, Carl George wrote: > Hello, > > I goofed and didn't read the contribute page before trying to create my > account on the wiki. I created the first account as "carlgeorge". I then > created a second account in the proper format, "CarlGeorge". Please delete > the first account. > You can change your username after the fact. > > Carl George > Rackspace RPM Development > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Fri May 1 17:36:22 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Fri, 1 May 2015 17:36:22 +0000 Subject: [CentOS-docs] delete account In-Reply-To: References: , Message-ID: <1430501744475.93987@RACKSPACE.COM> I tried that before I created the "CarlGeorge" account. It gave me an error stating that the user already existed (again, this was before I created the "CarlGeorge" account). However, just creating a new account as "CarlGeorge" worked. Please delete the "carlgeorge" account. The email account tied to it is the one I want to use on the "CarlGeorge" account. It won't let me change it. Carl George Rackspace RPM Development ________________________________ From: centos-docs-bounces at centos.org on behalf of Mike - st257 Sent: Friday, May 1, 2015 12:17 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] delete account On Thu, Apr 30, 2015 at 12:31 PM, Carl George > wrote: Hello, I goofed and didn't read the contribute page before trying to create my account on the wiki. I created the first account as "carlgeorge". I then created a second account in the proper format, "CarlGeorge". Please delete the first account. You can change your username after the fact. Carl George Rackspace RPM Development _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From amyagi at gmail.com Fri May 1 17:44:35 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Fri, 1 May 2015 10:44:35 -0700 Subject: [CentOS-docs] delete account In-Reply-To: <1430501744475.93987@RACKSPACE.COM> References: <1430501744475.93987@RACKSPACE.COM> Message-ID: On Fri, May 1, 2015 at 10:36 AM, Carl George wrote: > I tried that before I created the "CarlGeorge" account. It gave me an error > stating that the user already existed (again, this was before I created the > "CarlGeorge" account). However, just creating a new account as "CarlGeorge" > worked. > > Please delete the "carlgeorge" account. The email account tied to it is the > one I want to use on the "CarlGeorge" account. It won't let me change it. Ah, you should have mentioned that earlier. :) I see an account name carl.george. It now has a bogus email and the account is permanently disabled. Please confirm you have no issue with the "CarlGeorge" account. Deleting an account can only be done by administrators of the machine. But it's probably not necessary. Akemi From kwade at redhat.com Thu May 7 08:45:40 2015 From: kwade at redhat.com (Karsten Wade) Date: Thu, 07 May 2015 01:45:40 -0700 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <554B2634.8000808@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to welcome the two Summer of Code students who will be building different parts of the new CentOS documentation toolchain. * Kunal Jain * Lei Yang Students -- welcome again, and thank you for your work this far in helping define the project. Now we have the pleasure of working on the two new scopes that will work interdependently and independently. All of the discussion around this new toolchain has occurred on this mailing list, however the final accepted proposals are behind the GSoC webtool curtain. This is to our advantage, as we need to re-think the project plans across two students. As a refresher, here is the original idea: http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain And some relevant emails & threads: - From here: http://lists.centos.org/pipermail/centos-docs/2015-March/thread.html http://lists.centos.org/pipermail/centos-docs/2015-April/thread.html http://lists.centos.org/pipermail/centos-docs/2015-March/005593.html http://lists.centos.org/pipermail/centos-docs/2015-March/005594.html http://lists.centos.org/pipermail/centos-docs/2015-March/005618.html http://lists.centos.org/pipermail/centos-docs/2015-March/005620.html http://lists.centos.org/pipermail/centos-docs/2015-April/005623.html http://lists.centos.org/pipermail/centos-docs/2015-April/005624.html http://lists.centos.org/pipermail/centos-docs/2015-April/005629.html In discussions with the two students, myself, and Shaun McCance, we determined that we could effectively split up this project. That means the students will need to generate new work plans around individual scopes. These scopes will avoid overlap and interdependence so that each student is able to be successful without the others' project. So now the next fun part begins -- working out two scopes of work, the timing (as Kunaal's and Lei's schedules differ by a bit on either end of the summer), and what needs to be done in what order for all this to work. Cheers, - - 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) iEYEARECAAYFAlVLJjQACgkQ2ZIOBq0ODEEtnQCgsfpu4/EkRyShOKpgOuLZDUDz qO8AoOGTLXIMBWgmd6dg2NW9lR3H42y0 =TgvW -----END PGP SIGNATURE----- From kunaalus at gmail.com Thu May 7 13:14:36 2015 From: kunaalus at gmail.com (kunaal jain) Date: Thu, 7 May 2015 18:44:36 +0530 Subject: [CentOS-docs] Self Introduction [GSoC] Message-ID: Hi guys, I am Kunal Jain from India doing my undergraduate studies in Computer Science from Indian Institute of Technology Guwahati (IITG). I and Lei will be creating a new toolchain that will lower the barrier for contributing new content under the mentor-ship of Karsten this summer. I look forward working with you guys. More details : http://lists.centos.org/pipermail/centos-docs/2015-May/005647.html Regards, Kunal Jain -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Thu May 7 16:37:07 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 8 May 2015 00:37:07 +0800 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <887B9A98-85E9-450B-ADC4-119E14D68682@gmail.com> Thanks Karsten and nice to meet you :) I am looking forward to working with Kunal, Karsten and the community to build a new, easy-to-use docs toolchain for CentOS! I am Lei Yang from China, now studying at School of EECS, Peking University, China. In my original proposal, I think we may build an ?infrastructure?, moving docs between CentOS git repo and github. Then we build useful tools on that infrastructure to enable easier contribution and monitoring, all working with the git repo. I am happy to receive all ideas and suggestions! Thanks in advance! Lei From kbsingh at centos.org Tue May 12 10:13:14 2015 From: kbsingh at centos.org (Karanbir Singh) Date: Tue, 12 May 2015 11:13:14 +0100 Subject: [CentOS-docs] Container Pipeline placeholder Message-ID: <5551D23A.7000501@centos.org> Hi, I've created http://wiki.centos.org/ContainerPipleline as a placeholder to start populating about the pipeline. Although this will run from ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it will form a sort of ecocystem test + release process, I think it deserves scope beyond being just under the CI namespace. - KB -- 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 From lmohanty at redhat.com Tue May 12 10:19:38 2015 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Tue, 12 May 2015 15:49:38 +0530 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5551D3BA.7000307@redhat.com> On 05/12/2015 03:43 PM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. > > - KB > I [1] would like to contribute to the wiki page. So please give me write access. [1] http://wiki.centos.org/LalatenduMohanty Thanks, Lala From mail-lists at karan.org Tue May 12 10:43:59 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Tue, 12 May 2015 11:43:59 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D3BA.7000307@redhat.com> References: <5551D23A.7000501@centos.org> <5551D3BA.7000307@redhat.com> Message-ID: <5551D96F.1020209@karan.org> On 12/05/15 11:19, Lalatendu Mohanty wrote: > On 05/12/2015 03:43 PM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. >> >> - KB >> > > I [1] would like to contribute to the wiki page. So please give me write > access. > > [1] http://wiki.centos.org/LalatenduMohanty > done -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From kwade at redhat.com Wed May 13 05:29:01 2015 From: kwade at redhat.com (Karsten Wade) Date: Tue, 12 May 2015 22:29:01 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel Message-ID: <5552E11D.5030502@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a heads up that we're pulling together a last-hour discussion with the two GSoC students and myself in about 90 minutes in #centos-devel to discuss how the docs toolchain project will shape up - -- split the project, set timelines, and discuss resource needs. We'll post a log after the meeting is done, just wanted to send out a heads up in case anyone is a interesting in joining or lurking. Regards, - - 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) iEYEARECAAYFAlVS4R0ACgkQ2ZIOBq0ODEEAHwCg4R8FWTsAjDNhbqqjngJWoFvN IhsAoNcO8TTe9eBiNPUevqooIfc/V5Z9 =j41w -----END PGP SIGNATURE----- From kwade at redhat.com Wed May 13 13:58:30 2015 From: kwade at redhat.com (Karsten Wade) Date: Wed, 13 May 2015 06:58:30 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel In-Reply-To: <5552E11D.5030502@redhat.com> References: <5552E11D.5030502@redhat.com> Message-ID: <55535886.3010103@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://www.centos.org/minutes/2015/may/centos-devel.2015-05-13-07.08.htm l Minutes summary from above: ====================================== #centos-devel: Docs toolchain planning ====================================== Meeting started by quaid at 07:08:25 UTC. The full logs are available at centos-devel/2015/centos-devel.2015-05-13-07.08.log.html . Meeting summary - --------------- * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (quaid, 07:11:22) * LINK: https://cloud.githubusercontent.com/assets/7388044/6873628/b0b99aa4-d4d7 - -11e4-8aa6-7b25aa69585e.png (kunaaljain, 07:45:40) * LINK: https://docs.docker.com/ (kunaaljain, 07:59:21) * LINK: https://www.digitalocean.com/community/tutorials/?primary_filter=newes t (yangl1996, 08:00:16) * Need to figure out interaction with existing wiki content (refer in, publish to, etc.) (quaid, 08:55:34) * need to define the process and role for accepting changes in to git.centos.org (quaid, 08:56:10) * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (yangl1996, 09:01:53) Meeting ended at 09:31:49 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * yangl1996 (51) * kunaaljain (33) * quaid (31) * Arrfab (15) * centbot (2) * d0ugal (2) * Bahhumbug (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- 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) iEYEARECAAYFAlVTWIYACgkQ2ZIOBq0ODEHZgQCgqXd2VT6flMyFFimc++clW29h UasAn32egD2YC/I1MSejYW2cH2o4TIA1 =XN7+ -----END PGP SIGNATURE----- From jzb at redhat.com Thu May 14 14:35:46 2015 From: jzb at redhat.com (Joe Brockmeier) Date: Thu, 14 May 2015 10:35:46 -0400 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5554B2C2.5030902@redhat.com> On 05/12/2015 06:13 AM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. Pipleline? :-) Should that be: http://wiki.centos.org/ContainerPipeline ? Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From amyagi at gmail.com Thu May 14 14:54:49 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Thu, 14 May 2015 07:54:49 -0700 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5554B2C2.5030902@redhat.com> References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: > On 05/12/2015 06:13 AM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. > > Pipleline? :-) > > Should that be: > > http://wiki.centos.org/ContainerPipeline > > ? Funny that on one noticed. :) http://wiki.centos.org/ContainerPipeline?action=info Akemi From ajb at elrepo.org Thu May 14 15:05:10 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Thu, 14 May 2015 16:05:10 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On 14 May 2015 at 15:54, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info > > Akemi But I have noticed your typo! s/that on one/that no one/ I now claim my prize . . . :P Alan. From mail-lists at karan.org Thu May 14 15:04:22 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Thu, 14 May 2015 16:04:22 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: <5554B976.6070409@karan.org> On 05/14/2015 03:54 PM, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info someone did..! thanks -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From yltt1234512 at gmail.com Fri May 22 14:47:51 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 22 May 2015 22:47:51 +0800 Subject: [CentOS-docs] IRC Log - Kunaal and Lei - New Doc Toolchain - 05/20/2015 Message-ID: Hi! Kunaal and I had an IRC chat last Wednesday at UTC 0600. We discussed about the new docs toolchain. The first part of the chat log is about the workflow, here is the summary: 1. user write on local text editor / on github or a web based editor 2. the PR is created on github, and the info is synced to a reviewing platform, where staff discussed about, tag and accept the file 3. if the PR is accepted, the new article is synced from github to git.centos.org 4. new article is deployed and the doc site is updated 5. a tool convert the new article to different formats for upstream projects to use hey hi! So did u think anything about project I think something about the timeline tell me I think by midterm, we should generally finish half of the reviewing platform and the syncing tool Reviewing platform is definitely a big task yes we can ask on the mailing list for some existing open source project We have one and half month for the mid terms such as some bug tracking platform yes let's see tools required according to workflow First user writes a content Where does he write it? I thought about three ways: 1. he writes on local computer and push it to github 2. he write on a web-based editor 3. he write directly on github do you have other ideas? Sounds good to me. Github uses its own github markdown language So we adapt that? oh it is a problem i have no idea currently although adapting it will make the language more powerful, it is not "standard" markdown We can use that. its almost standard i think sounds good to me adapting this will help us using github tools good idea! about web - based editor. New editor or existing tools I think we can use existing tools, because developing a new editor is a huge task in my mind - if we have time after finishing other parts, we can build one Yeah, if we have left over time, we will do that. good idea! Okay so content is written A pull request has been created on github any other option? yes, totally agreed then what happens next? now that the content is on github, the staff should review it, tag it and comment on it Yes but what happens internally? Tool wise maybe the commit should trigger the syncing tool? there is no commit yet. Just a Pull Request so the commit info is synced to reviewing platform the staff need to review it and comment on it Maybe this pull request creates a issue in review platform yes, exactly what I think This review platform helps in tagging and commenting? yes Sounds good to me. Once the content is tagged and commented. Changes are made. yes, the staff accept the new content Then there should be an option to commit and close. exactly and the pull request can be merged in the repo on github once the commit is made, this is synced to git.c.o yes there involves some communication with github Yes one way sync? I think the communication happens in these situations: 1. github sync commit info to reviewing platform (create a issue on reviewing platfrom) 2. when staff accept the commit on reviewing platfrom, this actions is synced to github 3. the one way sync of repo data from github to git.c.o do you have some ideas? Yes. Also the issue needs to be synced i think yes! because staff comments and suggests changes exactly new changes are made on that pull request on github these changes have to be reflected on our platform so this should be a two-way sync yes I agree with you then 3rd point you made is correct one way sync from github to git.c.o yes once sync is done, Then new site has to be generated and deployed. we can use open source tools to do this Yes that sounds easy. Mkdocs we can use that ;) Then upstream projects :) yes we use pull model here a REST API? sounds good! This will take some time I guess. Totally a new model here I don't think previously it has been implemented yes, we need to build from bottom up I think so a have no idea about how open source projects share docs do they use some special format / conventions? I don't think there is such thing till now. so we have the basic workflow defined now? i think so so in basic tool chain what else we need don't know whether we need other parts do you have some ideas? I think what we discussed covers the basic part yes Content writing -> reviewing -> deployment -> upstream exactly what a doc system needs Yes. here is the ether pad link: http://etherpad.osuosl.org/CentOS-Docs-toolchain let's add the workflow to it Now I think it is very difficult to divide the proposed tools between us so that we can work independently so others can know our idea at once yes, so much dependency between parts Yeah definitely So What do you think? Working independently or together? Is it possible? if we will work in parallel, we need to define a set of APIs mainly between syncing tool and reviewing platform Defining before start is hard I think especially when we don?t know I think so! how reviewing platform will work yes exactly Development of it from scratch is not possible yes i am searching for some open source bug tracking platform Yes. We can modify it but we need the base yes So either we can work parallel and discuss everyday what we are doing, We can share work and problems I totally agree we need to sync our progress frequently maybe this will be of some use: http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems The list is quite big. You have a look at them, I will too ok! and I found centos is now using mantis as bug tracker: http://www.mantisbt.org/demo.php , I will see the features mantis supports centos doesnt use bugzilla? note that mantis is not open source oh! that's bad we need to use open source tools no no it is open source http://www.mantisbt.org/download.php https://github.com/mantisbt/mantisbt yeah! about the reviewing platform how do we implement it Ours requirement is not exactly as bug tracking we need to interact with github at each point i agree with you what we build is a platform syncing data with github realtime I think once we decide on review platform we can divide work and start but we need review platform details first i think yes let's discuss in in detail; yeah what can it do commenting, tagging just like github's issue tracking tool i think yes Exactly it is like bugzilla + github yes! so what we do for this? can we base the platform on bugzilla bugzilla meets our requirements? i think no we need to develop new features what about other platforms? the list you gave we need to integrate with git, so the choice narrows down a bit so the first task is find a reviewing platform can we do this by today so that we can meet up tomorrow or day after tomorrow again discuss the API and changes in platform yes exactly and start working on it ok! Regarding dividing work One option is we work parallel as reviewing platform definitely requries that we both work together yes so we can work together. the only con is we become dependent. We won;t be able to quantify our individual effort. It will like a team. I am okay with it I think I am okay, too Great! So let's hunt a review platform fast. Once we finalise that we will work on timeline and then finally start coding :D ok! I've narrowed down the choice from the list to a few open source projects :D Great. Keep me informed about the same. I will too look at them :) with requirement of supporting git and being open source, there are three choices from the list: http://www.fusionforge.org , http://www.redmine.org , http://trac.edgewall.org and bugzilla okay I am trying redming http://demo.redmine.org I registered an account so we can try the demo, login: gsoc_test password: gsoc_test I will try it :) :D ---------------- Lei -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Wed May 27 18:07:56 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 18:07:56 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal Message-ID: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Hello, I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html username: CarlGeorge proposed subject: Community Approved Third Party Repositories proposed location: http://wiki.centos.org/AdditionalResources/CATPR I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? Anyways, please create the article and grant me edit permission to it. Thanks! Carl George IUS CoreDev Team From ajb at elrepo.org Wed May 27 18:27:47 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 19:27:47 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Message-ID: On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR From carl.george at RACKSPACE.COM Wed May 27 21:36:59 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 21:36:59 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com>, Message-ID: <1432762564936.615@RACKSPACE.COM> Thanks Alan. While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? Carl George ________________________________________ From: centos-docs-bounces at centos.org on behalf of Alan Bartlett Sent: Wednesday, May 27, 2015 01:27 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] CATPR - new article for pending proposal On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs From ajb at elrepo.org Wed May 27 21:51:16 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 22:51:16 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <1432762564936.615@RACKSPACE.COM> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> <1432762564936.615@RACKSPACE.COM> Message-ID: On 27 May 2015 at 22:36, Carl George wrote: > Thanks Alan. > > While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? > > Carl George Sure. No problem. Alan. From carl.george at RACKSPACE.COM Thu May 28 23:04:35 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Thu, 28 May 2015 23:04:35 +0000 Subject: [CentOS-docs] proposal for Community Approved Third Party Repos (CATPR) Message-ID: <86aaddfe0e6348c6901a94c5013b4103@544124-OEXCH02.ror-uc.rackspace.com> Howdy, I am proposing a process for 3rd party repositories that would allow them to have their release RPM added the the CentOS Extras repository. http://wiki.centos.org/CarlGeorge/CATPR I would like to start a discussion about approving the proposal and how to move forward. Carl George IUS CoreDev Team From kunaalus at gmail.com Fri May 29 19:33:52 2015 From: kunaalus at gmail.com (kunaal jain) Date: Sat, 30 May 2015 01:03:52 +0530 Subject: [CentOS-docs] Regarding GSoC project Message-ID: 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-development/ Lei made a great chart comparing the platforms. https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing 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 ?? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dougal at dougalmatthews.com Sat May 30 16:19:35 2015 From: dougal at dougalmatthews.com (Dougal Matthews) Date: Sat, 30 May 2015 17:19:35 +0100 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: On 29 May 2015 at 20:33, kunaal jain wrote: > > 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-development/ > > Lei made a great chart comparing the platforms. > > https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing > > 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. As a word of warning here, not all Markdown parsers and renderers are the same. GitHub's makes a number of additions and changes that go against the original (admittedly vague) spec. This could mean your previews are different and may not match the documentation build. An alternative approach would be to build the docs in CI and link to the built version in a comment on both systems. > > Please let us know, what you think about this? > > Regards, > Kunaal > > > -- > Regards, > Kunaal Jain > > > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > From yltt1234512 at gmail.com Sun May 31 04:26:52 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:26:52 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: <745C8184-DCB1-451B-82BB-71AC124E3412@gmail.com> >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Sun May 31 04:37:02 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:37:02 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From silvertip257 at gmail.com Fri May 1 17:17:10 2015 From: silvertip257 at gmail.com (Mike - st257) Date: Fri, 1 May 2015 13:17:10 -0400 Subject: [CentOS-docs] delete account In-Reply-To: References: Message-ID: On Thu, Apr 30, 2015 at 12:31 PM, Carl George wrote: > Hello, > > I goofed and didn't read the contribute page before trying to create my > account on the wiki. I created the first account as "carlgeorge". I then > created a second account in the proper format, "CarlGeorge". Please delete > the first account. > You can change your username after the fact. > > Carl George > Rackspace RPM Development > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Fri May 1 17:36:22 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Fri, 1 May 2015 17:36:22 +0000 Subject: [CentOS-docs] delete account In-Reply-To: References: , Message-ID: <1430501744475.93987@RACKSPACE.COM> I tried that before I created the "CarlGeorge" account. It gave me an error stating that the user already existed (again, this was before I created the "CarlGeorge" account). However, just creating a new account as "CarlGeorge" worked. Please delete the "carlgeorge" account. The email account tied to it is the one I want to use on the "CarlGeorge" account. It won't let me change it. Carl George Rackspace RPM Development ________________________________ From: centos-docs-bounces at centos.org on behalf of Mike - st257 Sent: Friday, May 1, 2015 12:17 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] delete account On Thu, Apr 30, 2015 at 12:31 PM, Carl George > wrote: Hello, I goofed and didn't read the contribute page before trying to create my account on the wiki. I created the first account as "carlgeorge". I then created a second account in the proper format, "CarlGeorge". Please delete the first account. You can change your username after the fact. Carl George Rackspace RPM Development _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From amyagi at gmail.com Fri May 1 17:44:35 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Fri, 1 May 2015 10:44:35 -0700 Subject: [CentOS-docs] delete account In-Reply-To: <1430501744475.93987@RACKSPACE.COM> References: <1430501744475.93987@RACKSPACE.COM> Message-ID: On Fri, May 1, 2015 at 10:36 AM, Carl George wrote: > I tried that before I created the "CarlGeorge" account. It gave me an error > stating that the user already existed (again, this was before I created the > "CarlGeorge" account). However, just creating a new account as "CarlGeorge" > worked. > > Please delete the "carlgeorge" account. The email account tied to it is the > one I want to use on the "CarlGeorge" account. It won't let me change it. Ah, you should have mentioned that earlier. :) I see an account name carl.george. It now has a bogus email and the account is permanently disabled. Please confirm you have no issue with the "CarlGeorge" account. Deleting an account can only be done by administrators of the machine. But it's probably not necessary. Akemi From kwade at redhat.com Thu May 7 08:45:40 2015 From: kwade at redhat.com (Karsten Wade) Date: Thu, 07 May 2015 01:45:40 -0700 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <554B2634.8000808@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to welcome the two Summer of Code students who will be building different parts of the new CentOS documentation toolchain. * Kunal Jain * Lei Yang Students -- welcome again, and thank you for your work this far in helping define the project. Now we have the pleasure of working on the two new scopes that will work interdependently and independently. All of the discussion around this new toolchain has occurred on this mailing list, however the final accepted proposals are behind the GSoC webtool curtain. This is to our advantage, as we need to re-think the project plans across two students. As a refresher, here is the original idea: http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain And some relevant emails & threads: - From here: http://lists.centos.org/pipermail/centos-docs/2015-March/thread.html http://lists.centos.org/pipermail/centos-docs/2015-April/thread.html http://lists.centos.org/pipermail/centos-docs/2015-March/005593.html http://lists.centos.org/pipermail/centos-docs/2015-March/005594.html http://lists.centos.org/pipermail/centos-docs/2015-March/005618.html http://lists.centos.org/pipermail/centos-docs/2015-March/005620.html http://lists.centos.org/pipermail/centos-docs/2015-April/005623.html http://lists.centos.org/pipermail/centos-docs/2015-April/005624.html http://lists.centos.org/pipermail/centos-docs/2015-April/005629.html In discussions with the two students, myself, and Shaun McCance, we determined that we could effectively split up this project. That means the students will need to generate new work plans around individual scopes. These scopes will avoid overlap and interdependence so that each student is able to be successful without the others' project. So now the next fun part begins -- working out two scopes of work, the timing (as Kunaal's and Lei's schedules differ by a bit on either end of the summer), and what needs to be done in what order for all this to work. Cheers, - - 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) iEYEARECAAYFAlVLJjQACgkQ2ZIOBq0ODEEtnQCgsfpu4/EkRyShOKpgOuLZDUDz qO8AoOGTLXIMBWgmd6dg2NW9lR3H42y0 =TgvW -----END PGP SIGNATURE----- From kunaalus at gmail.com Thu May 7 13:14:36 2015 From: kunaalus at gmail.com (kunaal jain) Date: Thu, 7 May 2015 18:44:36 +0530 Subject: [CentOS-docs] Self Introduction [GSoC] Message-ID: Hi guys, I am Kunal Jain from India doing my undergraduate studies in Computer Science from Indian Institute of Technology Guwahati (IITG). I and Lei will be creating a new toolchain that will lower the barrier for contributing new content under the mentor-ship of Karsten this summer. I look forward working with you guys. More details : http://lists.centos.org/pipermail/centos-docs/2015-May/005647.html Regards, Kunal Jain -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Thu May 7 16:37:07 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 8 May 2015 00:37:07 +0800 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <887B9A98-85E9-450B-ADC4-119E14D68682@gmail.com> Thanks Karsten and nice to meet you :) I am looking forward to working with Kunal, Karsten and the community to build a new, easy-to-use docs toolchain for CentOS! I am Lei Yang from China, now studying at School of EECS, Peking University, China. In my original proposal, I think we may build an ?infrastructure?, moving docs between CentOS git repo and github. Then we build useful tools on that infrastructure to enable easier contribution and monitoring, all working with the git repo. I am happy to receive all ideas and suggestions! Thanks in advance! Lei From kbsingh at centos.org Tue May 12 10:13:14 2015 From: kbsingh at centos.org (Karanbir Singh) Date: Tue, 12 May 2015 11:13:14 +0100 Subject: [CentOS-docs] Container Pipeline placeholder Message-ID: <5551D23A.7000501@centos.org> Hi, I've created http://wiki.centos.org/ContainerPipleline as a placeholder to start populating about the pipeline. Although this will run from ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it will form a sort of ecocystem test + release process, I think it deserves scope beyond being just under the CI namespace. - KB -- 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 From lmohanty at redhat.com Tue May 12 10:19:38 2015 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Tue, 12 May 2015 15:49:38 +0530 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5551D3BA.7000307@redhat.com> On 05/12/2015 03:43 PM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. > > - KB > I [1] would like to contribute to the wiki page. So please give me write access. [1] http://wiki.centos.org/LalatenduMohanty Thanks, Lala From mail-lists at karan.org Tue May 12 10:43:59 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Tue, 12 May 2015 11:43:59 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D3BA.7000307@redhat.com> References: <5551D23A.7000501@centos.org> <5551D3BA.7000307@redhat.com> Message-ID: <5551D96F.1020209@karan.org> On 12/05/15 11:19, Lalatendu Mohanty wrote: > On 05/12/2015 03:43 PM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. >> >> - KB >> > > I [1] would like to contribute to the wiki page. So please give me write > access. > > [1] http://wiki.centos.org/LalatenduMohanty > done -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From kwade at redhat.com Wed May 13 05:29:01 2015 From: kwade at redhat.com (Karsten Wade) Date: Tue, 12 May 2015 22:29:01 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel Message-ID: <5552E11D.5030502@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a heads up that we're pulling together a last-hour discussion with the two GSoC students and myself in about 90 minutes in #centos-devel to discuss how the docs toolchain project will shape up - -- split the project, set timelines, and discuss resource needs. We'll post a log after the meeting is done, just wanted to send out a heads up in case anyone is a interesting in joining or lurking. Regards, - - 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) iEYEARECAAYFAlVS4R0ACgkQ2ZIOBq0ODEEAHwCg4R8FWTsAjDNhbqqjngJWoFvN IhsAoNcO8TTe9eBiNPUevqooIfc/V5Z9 =j41w -----END PGP SIGNATURE----- From kwade at redhat.com Wed May 13 13:58:30 2015 From: kwade at redhat.com (Karsten Wade) Date: Wed, 13 May 2015 06:58:30 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel In-Reply-To: <5552E11D.5030502@redhat.com> References: <5552E11D.5030502@redhat.com> Message-ID: <55535886.3010103@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://www.centos.org/minutes/2015/may/centos-devel.2015-05-13-07.08.htm l Minutes summary from above: ====================================== #centos-devel: Docs toolchain planning ====================================== Meeting started by quaid at 07:08:25 UTC. The full logs are available at centos-devel/2015/centos-devel.2015-05-13-07.08.log.html . Meeting summary - --------------- * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (quaid, 07:11:22) * LINK: https://cloud.githubusercontent.com/assets/7388044/6873628/b0b99aa4-d4d7 - -11e4-8aa6-7b25aa69585e.png (kunaaljain, 07:45:40) * LINK: https://docs.docker.com/ (kunaaljain, 07:59:21) * LINK: https://www.digitalocean.com/community/tutorials/?primary_filter=newes t (yangl1996, 08:00:16) * Need to figure out interaction with existing wiki content (refer in, publish to, etc.) (quaid, 08:55:34) * need to define the process and role for accepting changes in to git.centos.org (quaid, 08:56:10) * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (yangl1996, 09:01:53) Meeting ended at 09:31:49 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * yangl1996 (51) * kunaaljain (33) * quaid (31) * Arrfab (15) * centbot (2) * d0ugal (2) * Bahhumbug (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- 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) iEYEARECAAYFAlVTWIYACgkQ2ZIOBq0ODEHZgQCgqXd2VT6flMyFFimc++clW29h UasAn32egD2YC/I1MSejYW2cH2o4TIA1 =XN7+ -----END PGP SIGNATURE----- From jzb at redhat.com Thu May 14 14:35:46 2015 From: jzb at redhat.com (Joe Brockmeier) Date: Thu, 14 May 2015 10:35:46 -0400 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5554B2C2.5030902@redhat.com> On 05/12/2015 06:13 AM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. Pipleline? :-) Should that be: http://wiki.centos.org/ContainerPipeline ? Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From amyagi at gmail.com Thu May 14 14:54:49 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Thu, 14 May 2015 07:54:49 -0700 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5554B2C2.5030902@redhat.com> References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: > On 05/12/2015 06:13 AM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. > > Pipleline? :-) > > Should that be: > > http://wiki.centos.org/ContainerPipeline > > ? Funny that on one noticed. :) http://wiki.centos.org/ContainerPipeline?action=info Akemi From ajb at elrepo.org Thu May 14 15:05:10 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Thu, 14 May 2015 16:05:10 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On 14 May 2015 at 15:54, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info > > Akemi But I have noticed your typo! s/that on one/that no one/ I now claim my prize . . . :P Alan. From mail-lists at karan.org Thu May 14 15:04:22 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Thu, 14 May 2015 16:04:22 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: <5554B976.6070409@karan.org> On 05/14/2015 03:54 PM, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info someone did..! thanks -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From yltt1234512 at gmail.com Fri May 22 14:47:51 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 22 May 2015 22:47:51 +0800 Subject: [CentOS-docs] IRC Log - Kunaal and Lei - New Doc Toolchain - 05/20/2015 Message-ID: Hi! Kunaal and I had an IRC chat last Wednesday at UTC 0600. We discussed about the new docs toolchain. The first part of the chat log is about the workflow, here is the summary: 1. user write on local text editor / on github or a web based editor 2. the PR is created on github, and the info is synced to a reviewing platform, where staff discussed about, tag and accept the file 3. if the PR is accepted, the new article is synced from github to git.centos.org 4. new article is deployed and the doc site is updated 5. a tool convert the new article to different formats for upstream projects to use hey hi! So did u think anything about project I think something about the timeline tell me I think by midterm, we should generally finish half of the reviewing platform and the syncing tool Reviewing platform is definitely a big task yes we can ask on the mailing list for some existing open source project We have one and half month for the mid terms such as some bug tracking platform yes let's see tools required according to workflow First user writes a content Where does he write it? I thought about three ways: 1. he writes on local computer and push it to github 2. he write on a web-based editor 3. he write directly on github do you have other ideas? Sounds good to me. Github uses its own github markdown language So we adapt that? oh it is a problem i have no idea currently although adapting it will make the language more powerful, it is not "standard" markdown We can use that. its almost standard i think sounds good to me adapting this will help us using github tools good idea! about web - based editor. New editor or existing tools I think we can use existing tools, because developing a new editor is a huge task in my mind - if we have time after finishing other parts, we can build one Yeah, if we have left over time, we will do that. good idea! Okay so content is written A pull request has been created on github any other option? yes, totally agreed then what happens next? now that the content is on github, the staff should review it, tag it and comment on it Yes but what happens internally? Tool wise maybe the commit should trigger the syncing tool? there is no commit yet. Just a Pull Request so the commit info is synced to reviewing platform the staff need to review it and comment on it Maybe this pull request creates a issue in review platform yes, exactly what I think This review platform helps in tagging and commenting? yes Sounds good to me. Once the content is tagged and commented. Changes are made. yes, the staff accept the new content Then there should be an option to commit and close. exactly and the pull request can be merged in the repo on github once the commit is made, this is synced to git.c.o yes there involves some communication with github Yes one way sync? I think the communication happens in these situations: 1. github sync commit info to reviewing platform (create a issue on reviewing platfrom) 2. when staff accept the commit on reviewing platfrom, this actions is synced to github 3. the one way sync of repo data from github to git.c.o do you have some ideas? Yes. Also the issue needs to be synced i think yes! because staff comments and suggests changes exactly new changes are made on that pull request on github these changes have to be reflected on our platform so this should be a two-way sync yes I agree with you then 3rd point you made is correct one way sync from github to git.c.o yes once sync is done, Then new site has to be generated and deployed. we can use open source tools to do this Yes that sounds easy. Mkdocs we can use that ;) Then upstream projects :) yes we use pull model here a REST API? sounds good! This will take some time I guess. Totally a new model here I don't think previously it has been implemented yes, we need to build from bottom up I think so a have no idea about how open source projects share docs do they use some special format / conventions? I don't think there is such thing till now. so we have the basic workflow defined now? i think so so in basic tool chain what else we need don't know whether we need other parts do you have some ideas? I think what we discussed covers the basic part yes Content writing -> reviewing -> deployment -> upstream exactly what a doc system needs Yes. here is the ether pad link: http://etherpad.osuosl.org/CentOS-Docs-toolchain let's add the workflow to it Now I think it is very difficult to divide the proposed tools between us so that we can work independently so others can know our idea at once yes, so much dependency between parts Yeah definitely So What do you think? Working independently or together? Is it possible? if we will work in parallel, we need to define a set of APIs mainly between syncing tool and reviewing platform Defining before start is hard I think especially when we don?t know I think so! how reviewing platform will work yes exactly Development of it from scratch is not possible yes i am searching for some open source bug tracking platform Yes. We can modify it but we need the base yes So either we can work parallel and discuss everyday what we are doing, We can share work and problems I totally agree we need to sync our progress frequently maybe this will be of some use: http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems The list is quite big. You have a look at them, I will too ok! and I found centos is now using mantis as bug tracker: http://www.mantisbt.org/demo.php , I will see the features mantis supports centos doesnt use bugzilla? note that mantis is not open source oh! that's bad we need to use open source tools no no it is open source http://www.mantisbt.org/download.php https://github.com/mantisbt/mantisbt yeah! about the reviewing platform how do we implement it Ours requirement is not exactly as bug tracking we need to interact with github at each point i agree with you what we build is a platform syncing data with github realtime I think once we decide on review platform we can divide work and start but we need review platform details first i think yes let's discuss in in detail; yeah what can it do commenting, tagging just like github's issue tracking tool i think yes Exactly it is like bugzilla + github yes! so what we do for this? can we base the platform on bugzilla bugzilla meets our requirements? i think no we need to develop new features what about other platforms? the list you gave we need to integrate with git, so the choice narrows down a bit so the first task is find a reviewing platform can we do this by today so that we can meet up tomorrow or day after tomorrow again discuss the API and changes in platform yes exactly and start working on it ok! Regarding dividing work One option is we work parallel as reviewing platform definitely requries that we both work together yes so we can work together. the only con is we become dependent. We won;t be able to quantify our individual effort. It will like a team. I am okay with it I think I am okay, too Great! So let's hunt a review platform fast. Once we finalise that we will work on timeline and then finally start coding :D ok! I've narrowed down the choice from the list to a few open source projects :D Great. Keep me informed about the same. I will too look at them :) with requirement of supporting git and being open source, there are three choices from the list: http://www.fusionforge.org , http://www.redmine.org , http://trac.edgewall.org and bugzilla okay I am trying redming http://demo.redmine.org I registered an account so we can try the demo, login: gsoc_test password: gsoc_test I will try it :) :D ---------------- Lei -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Wed May 27 18:07:56 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 18:07:56 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal Message-ID: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Hello, I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html username: CarlGeorge proposed subject: Community Approved Third Party Repositories proposed location: http://wiki.centos.org/AdditionalResources/CATPR I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? Anyways, please create the article and grant me edit permission to it. Thanks! Carl George IUS CoreDev Team From ajb at elrepo.org Wed May 27 18:27:47 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 19:27:47 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Message-ID: On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR From carl.george at RACKSPACE.COM Wed May 27 21:36:59 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 21:36:59 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com>, Message-ID: <1432762564936.615@RACKSPACE.COM> Thanks Alan. While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? Carl George ________________________________________ From: centos-docs-bounces at centos.org on behalf of Alan Bartlett Sent: Wednesday, May 27, 2015 01:27 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] CATPR - new article for pending proposal On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs From ajb at elrepo.org Wed May 27 21:51:16 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 22:51:16 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <1432762564936.615@RACKSPACE.COM> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> <1432762564936.615@RACKSPACE.COM> Message-ID: On 27 May 2015 at 22:36, Carl George wrote: > Thanks Alan. > > While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? > > Carl George Sure. No problem. Alan. From carl.george at RACKSPACE.COM Thu May 28 23:04:35 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Thu, 28 May 2015 23:04:35 +0000 Subject: [CentOS-docs] proposal for Community Approved Third Party Repos (CATPR) Message-ID: <86aaddfe0e6348c6901a94c5013b4103@544124-OEXCH02.ror-uc.rackspace.com> Howdy, I am proposing a process for 3rd party repositories that would allow them to have their release RPM added the the CentOS Extras repository. http://wiki.centos.org/CarlGeorge/CATPR I would like to start a discussion about approving the proposal and how to move forward. Carl George IUS CoreDev Team From kunaalus at gmail.com Fri May 29 19:33:52 2015 From: kunaalus at gmail.com (kunaal jain) Date: Sat, 30 May 2015 01:03:52 +0530 Subject: [CentOS-docs] Regarding GSoC project Message-ID: 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-development/ Lei made a great chart comparing the platforms. https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing 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 ?? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dougal at dougalmatthews.com Sat May 30 16:19:35 2015 From: dougal at dougalmatthews.com (Dougal Matthews) Date: Sat, 30 May 2015 17:19:35 +0100 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: On 29 May 2015 at 20:33, kunaal jain wrote: > > 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-development/ > > Lei made a great chart comparing the platforms. > > https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing > > 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. As a word of warning here, not all Markdown parsers and renderers are the same. GitHub's makes a number of additions and changes that go against the original (admittedly vague) spec. This could mean your previews are different and may not match the documentation build. An alternative approach would be to build the docs in CI and link to the built version in a comment on both systems. > > Please let us know, what you think about this? > > Regards, > Kunaal > > > -- > Regards, > Kunaal Jain > > > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > From yltt1234512 at gmail.com Sun May 31 04:26:52 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:26:52 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: <745C8184-DCB1-451B-82BB-71AC124E3412@gmail.com> >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Sun May 31 04:37:02 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:37:02 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From silvertip257 at gmail.com Fri May 1 17:17:10 2015 From: silvertip257 at gmail.com (Mike - st257) Date: Fri, 1 May 2015 13:17:10 -0400 Subject: [CentOS-docs] delete account In-Reply-To: References: Message-ID: On Thu, Apr 30, 2015 at 12:31 PM, Carl George wrote: > Hello, > > I goofed and didn't read the contribute page before trying to create my > account on the wiki. I created the first account as "carlgeorge". I then > created a second account in the proper format, "CarlGeorge". Please delete > the first account. > You can change your username after the fact. > > Carl George > Rackspace RPM Development > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Fri May 1 17:36:22 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Fri, 1 May 2015 17:36:22 +0000 Subject: [CentOS-docs] delete account In-Reply-To: References: , Message-ID: <1430501744475.93987@RACKSPACE.COM> I tried that before I created the "CarlGeorge" account. It gave me an error stating that the user already existed (again, this was before I created the "CarlGeorge" account). However, just creating a new account as "CarlGeorge" worked. Please delete the "carlgeorge" account. The email account tied to it is the one I want to use on the "CarlGeorge" account. It won't let me change it. Carl George Rackspace RPM Development ________________________________ From: centos-docs-bounces at centos.org on behalf of Mike - st257 Sent: Friday, May 1, 2015 12:17 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] delete account On Thu, Apr 30, 2015 at 12:31 PM, Carl George > wrote: Hello, I goofed and didn't read the contribute page before trying to create my account on the wiki. I created the first account as "carlgeorge". I then created a second account in the proper format, "CarlGeorge". Please delete the first account. You can change your username after the fact. Carl George Rackspace RPM Development _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From amyagi at gmail.com Fri May 1 17:44:35 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Fri, 1 May 2015 10:44:35 -0700 Subject: [CentOS-docs] delete account In-Reply-To: <1430501744475.93987@RACKSPACE.COM> References: <1430501744475.93987@RACKSPACE.COM> Message-ID: On Fri, May 1, 2015 at 10:36 AM, Carl George wrote: > I tried that before I created the "CarlGeorge" account. It gave me an error > stating that the user already existed (again, this was before I created the > "CarlGeorge" account). However, just creating a new account as "CarlGeorge" > worked. > > Please delete the "carlgeorge" account. The email account tied to it is the > one I want to use on the "CarlGeorge" account. It won't let me change it. Ah, you should have mentioned that earlier. :) I see an account name carl.george. It now has a bogus email and the account is permanently disabled. Please confirm you have no issue with the "CarlGeorge" account. Deleting an account can only be done by administrators of the machine. But it's probably not necessary. Akemi From kwade at redhat.com Thu May 7 08:45:40 2015 From: kwade at redhat.com (Karsten Wade) Date: Thu, 07 May 2015 01:45:40 -0700 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <554B2634.8000808@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to welcome the two Summer of Code students who will be building different parts of the new CentOS documentation toolchain. * Kunal Jain * Lei Yang Students -- welcome again, and thank you for your work this far in helping define the project. Now we have the pleasure of working on the two new scopes that will work interdependently and independently. All of the discussion around this new toolchain has occurred on this mailing list, however the final accepted proposals are behind the GSoC webtool curtain. This is to our advantage, as we need to re-think the project plans across two students. As a refresher, here is the original idea: http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain And some relevant emails & threads: - From here: http://lists.centos.org/pipermail/centos-docs/2015-March/thread.html http://lists.centos.org/pipermail/centos-docs/2015-April/thread.html http://lists.centos.org/pipermail/centos-docs/2015-March/005593.html http://lists.centos.org/pipermail/centos-docs/2015-March/005594.html http://lists.centos.org/pipermail/centos-docs/2015-March/005618.html http://lists.centos.org/pipermail/centos-docs/2015-March/005620.html http://lists.centos.org/pipermail/centos-docs/2015-April/005623.html http://lists.centos.org/pipermail/centos-docs/2015-April/005624.html http://lists.centos.org/pipermail/centos-docs/2015-April/005629.html In discussions with the two students, myself, and Shaun McCance, we determined that we could effectively split up this project. That means the students will need to generate new work plans around individual scopes. These scopes will avoid overlap and interdependence so that each student is able to be successful without the others' project. So now the next fun part begins -- working out two scopes of work, the timing (as Kunaal's and Lei's schedules differ by a bit on either end of the summer), and what needs to be done in what order for all this to work. Cheers, - - 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) iEYEARECAAYFAlVLJjQACgkQ2ZIOBq0ODEEtnQCgsfpu4/EkRyShOKpgOuLZDUDz qO8AoOGTLXIMBWgmd6dg2NW9lR3H42y0 =TgvW -----END PGP SIGNATURE----- From kunaalus at gmail.com Thu May 7 13:14:36 2015 From: kunaalus at gmail.com (kunaal jain) Date: Thu, 7 May 2015 18:44:36 +0530 Subject: [CentOS-docs] Self Introduction [GSoC] Message-ID: Hi guys, I am Kunal Jain from India doing my undergraduate studies in Computer Science from Indian Institute of Technology Guwahati (IITG). I and Lei will be creating a new toolchain that will lower the barrier for contributing new content under the mentor-ship of Karsten this summer. I look forward working with you guys. More details : http://lists.centos.org/pipermail/centos-docs/2015-May/005647.html Regards, Kunal Jain -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Thu May 7 16:37:07 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 8 May 2015 00:37:07 +0800 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <887B9A98-85E9-450B-ADC4-119E14D68682@gmail.com> Thanks Karsten and nice to meet you :) I am looking forward to working with Kunal, Karsten and the community to build a new, easy-to-use docs toolchain for CentOS! I am Lei Yang from China, now studying at School of EECS, Peking University, China. In my original proposal, I think we may build an ?infrastructure?, moving docs between CentOS git repo and github. Then we build useful tools on that infrastructure to enable easier contribution and monitoring, all working with the git repo. I am happy to receive all ideas and suggestions! Thanks in advance! Lei From kbsingh at centos.org Tue May 12 10:13:14 2015 From: kbsingh at centos.org (Karanbir Singh) Date: Tue, 12 May 2015 11:13:14 +0100 Subject: [CentOS-docs] Container Pipeline placeholder Message-ID: <5551D23A.7000501@centos.org> Hi, I've created http://wiki.centos.org/ContainerPipleline as a placeholder to start populating about the pipeline. Although this will run from ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it will form a sort of ecocystem test + release process, I think it deserves scope beyond being just under the CI namespace. - KB -- 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 From lmohanty at redhat.com Tue May 12 10:19:38 2015 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Tue, 12 May 2015 15:49:38 +0530 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5551D3BA.7000307@redhat.com> On 05/12/2015 03:43 PM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. > > - KB > I [1] would like to contribute to the wiki page. So please give me write access. [1] http://wiki.centos.org/LalatenduMohanty Thanks, Lala From mail-lists at karan.org Tue May 12 10:43:59 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Tue, 12 May 2015 11:43:59 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D3BA.7000307@redhat.com> References: <5551D23A.7000501@centos.org> <5551D3BA.7000307@redhat.com> Message-ID: <5551D96F.1020209@karan.org> On 12/05/15 11:19, Lalatendu Mohanty wrote: > On 05/12/2015 03:43 PM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. >> >> - KB >> > > I [1] would like to contribute to the wiki page. So please give me write > access. > > [1] http://wiki.centos.org/LalatenduMohanty > done -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From kwade at redhat.com Wed May 13 05:29:01 2015 From: kwade at redhat.com (Karsten Wade) Date: Tue, 12 May 2015 22:29:01 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel Message-ID: <5552E11D.5030502@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a heads up that we're pulling together a last-hour discussion with the two GSoC students and myself in about 90 minutes in #centos-devel to discuss how the docs toolchain project will shape up - -- split the project, set timelines, and discuss resource needs. We'll post a log after the meeting is done, just wanted to send out a heads up in case anyone is a interesting in joining or lurking. Regards, - - 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) iEYEARECAAYFAlVS4R0ACgkQ2ZIOBq0ODEEAHwCg4R8FWTsAjDNhbqqjngJWoFvN IhsAoNcO8TTe9eBiNPUevqooIfc/V5Z9 =j41w -----END PGP SIGNATURE----- From kwade at redhat.com Wed May 13 13:58:30 2015 From: kwade at redhat.com (Karsten Wade) Date: Wed, 13 May 2015 06:58:30 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel In-Reply-To: <5552E11D.5030502@redhat.com> References: <5552E11D.5030502@redhat.com> Message-ID: <55535886.3010103@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://www.centos.org/minutes/2015/may/centos-devel.2015-05-13-07.08.htm l Minutes summary from above: ====================================== #centos-devel: Docs toolchain planning ====================================== Meeting started by quaid at 07:08:25 UTC. The full logs are available at centos-devel/2015/centos-devel.2015-05-13-07.08.log.html . Meeting summary - --------------- * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (quaid, 07:11:22) * LINK: https://cloud.githubusercontent.com/assets/7388044/6873628/b0b99aa4-d4d7 - -11e4-8aa6-7b25aa69585e.png (kunaaljain, 07:45:40) * LINK: https://docs.docker.com/ (kunaaljain, 07:59:21) * LINK: https://www.digitalocean.com/community/tutorials/?primary_filter=newes t (yangl1996, 08:00:16) * Need to figure out interaction with existing wiki content (refer in, publish to, etc.) (quaid, 08:55:34) * need to define the process and role for accepting changes in to git.centos.org (quaid, 08:56:10) * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (yangl1996, 09:01:53) Meeting ended at 09:31:49 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * yangl1996 (51) * kunaaljain (33) * quaid (31) * Arrfab (15) * centbot (2) * d0ugal (2) * Bahhumbug (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- 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) iEYEARECAAYFAlVTWIYACgkQ2ZIOBq0ODEHZgQCgqXd2VT6flMyFFimc++clW29h UasAn32egD2YC/I1MSejYW2cH2o4TIA1 =XN7+ -----END PGP SIGNATURE----- From jzb at redhat.com Thu May 14 14:35:46 2015 From: jzb at redhat.com (Joe Brockmeier) Date: Thu, 14 May 2015 10:35:46 -0400 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5554B2C2.5030902@redhat.com> On 05/12/2015 06:13 AM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. Pipleline? :-) Should that be: http://wiki.centos.org/ContainerPipeline ? Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From amyagi at gmail.com Thu May 14 14:54:49 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Thu, 14 May 2015 07:54:49 -0700 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5554B2C2.5030902@redhat.com> References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: > On 05/12/2015 06:13 AM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. > > Pipleline? :-) > > Should that be: > > http://wiki.centos.org/ContainerPipeline > > ? Funny that on one noticed. :) http://wiki.centos.org/ContainerPipeline?action=info Akemi From ajb at elrepo.org Thu May 14 15:05:10 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Thu, 14 May 2015 16:05:10 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On 14 May 2015 at 15:54, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info > > Akemi But I have noticed your typo! s/that on one/that no one/ I now claim my prize . . . :P Alan. From mail-lists at karan.org Thu May 14 15:04:22 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Thu, 14 May 2015 16:04:22 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: <5554B976.6070409@karan.org> On 05/14/2015 03:54 PM, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info someone did..! thanks -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From yltt1234512 at gmail.com Fri May 22 14:47:51 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 22 May 2015 22:47:51 +0800 Subject: [CentOS-docs] IRC Log - Kunaal and Lei - New Doc Toolchain - 05/20/2015 Message-ID: Hi! Kunaal and I had an IRC chat last Wednesday at UTC 0600. We discussed about the new docs toolchain. The first part of the chat log is about the workflow, here is the summary: 1. user write on local text editor / on github or a web based editor 2. the PR is created on github, and the info is synced to a reviewing platform, where staff discussed about, tag and accept the file 3. if the PR is accepted, the new article is synced from github to git.centos.org 4. new article is deployed and the doc site is updated 5. a tool convert the new article to different formats for upstream projects to use hey hi! So did u think anything about project I think something about the timeline tell me I think by midterm, we should generally finish half of the reviewing platform and the syncing tool Reviewing platform is definitely a big task yes we can ask on the mailing list for some existing open source project We have one and half month for the mid terms such as some bug tracking platform yes let's see tools required according to workflow First user writes a content Where does he write it? I thought about three ways: 1. he writes on local computer and push it to github 2. he write on a web-based editor 3. he write directly on github do you have other ideas? Sounds good to me. Github uses its own github markdown language So we adapt that? oh it is a problem i have no idea currently although adapting it will make the language more powerful, it is not "standard" markdown We can use that. its almost standard i think sounds good to me adapting this will help us using github tools good idea! about web - based editor. New editor or existing tools I think we can use existing tools, because developing a new editor is a huge task in my mind - if we have time after finishing other parts, we can build one Yeah, if we have left over time, we will do that. good idea! Okay so content is written A pull request has been created on github any other option? yes, totally agreed then what happens next? now that the content is on github, the staff should review it, tag it and comment on it Yes but what happens internally? Tool wise maybe the commit should trigger the syncing tool? there is no commit yet. Just a Pull Request so the commit info is synced to reviewing platform the staff need to review it and comment on it Maybe this pull request creates a issue in review platform yes, exactly what I think This review platform helps in tagging and commenting? yes Sounds good to me. Once the content is tagged and commented. Changes are made. yes, the staff accept the new content Then there should be an option to commit and close. exactly and the pull request can be merged in the repo on github once the commit is made, this is synced to git.c.o yes there involves some communication with github Yes one way sync? I think the communication happens in these situations: 1. github sync commit info to reviewing platform (create a issue on reviewing platfrom) 2. when staff accept the commit on reviewing platfrom, this actions is synced to github 3. the one way sync of repo data from github to git.c.o do you have some ideas? Yes. Also the issue needs to be synced i think yes! because staff comments and suggests changes exactly new changes are made on that pull request on github these changes have to be reflected on our platform so this should be a two-way sync yes I agree with you then 3rd point you made is correct one way sync from github to git.c.o yes once sync is done, Then new site has to be generated and deployed. we can use open source tools to do this Yes that sounds easy. Mkdocs we can use that ;) Then upstream projects :) yes we use pull model here a REST API? sounds good! This will take some time I guess. Totally a new model here I don't think previously it has been implemented yes, we need to build from bottom up I think so a have no idea about how open source projects share docs do they use some special format / conventions? I don't think there is such thing till now. so we have the basic workflow defined now? i think so so in basic tool chain what else we need don't know whether we need other parts do you have some ideas? I think what we discussed covers the basic part yes Content writing -> reviewing -> deployment -> upstream exactly what a doc system needs Yes. here is the ether pad link: http://etherpad.osuosl.org/CentOS-Docs-toolchain let's add the workflow to it Now I think it is very difficult to divide the proposed tools between us so that we can work independently so others can know our idea at once yes, so much dependency between parts Yeah definitely So What do you think? Working independently or together? Is it possible? if we will work in parallel, we need to define a set of APIs mainly between syncing tool and reviewing platform Defining before start is hard I think especially when we don?t know I think so! how reviewing platform will work yes exactly Development of it from scratch is not possible yes i am searching for some open source bug tracking platform Yes. We can modify it but we need the base yes So either we can work parallel and discuss everyday what we are doing, We can share work and problems I totally agree we need to sync our progress frequently maybe this will be of some use: http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems The list is quite big. You have a look at them, I will too ok! and I found centos is now using mantis as bug tracker: http://www.mantisbt.org/demo.php , I will see the features mantis supports centos doesnt use bugzilla? note that mantis is not open source oh! that's bad we need to use open source tools no no it is open source http://www.mantisbt.org/download.php https://github.com/mantisbt/mantisbt yeah! about the reviewing platform how do we implement it Ours requirement is not exactly as bug tracking we need to interact with github at each point i agree with you what we build is a platform syncing data with github realtime I think once we decide on review platform we can divide work and start but we need review platform details first i think yes let's discuss in in detail; yeah what can it do commenting, tagging just like github's issue tracking tool i think yes Exactly it is like bugzilla + github yes! so what we do for this? can we base the platform on bugzilla bugzilla meets our requirements? i think no we need to develop new features what about other platforms? the list you gave we need to integrate with git, so the choice narrows down a bit so the first task is find a reviewing platform can we do this by today so that we can meet up tomorrow or day after tomorrow again discuss the API and changes in platform yes exactly and start working on it ok! Regarding dividing work One option is we work parallel as reviewing platform definitely requries that we both work together yes so we can work together. the only con is we become dependent. We won;t be able to quantify our individual effort. It will like a team. I am okay with it I think I am okay, too Great! So let's hunt a review platform fast. Once we finalise that we will work on timeline and then finally start coding :D ok! I've narrowed down the choice from the list to a few open source projects :D Great. Keep me informed about the same. I will too look at them :) with requirement of supporting git and being open source, there are three choices from the list: http://www.fusionforge.org , http://www.redmine.org , http://trac.edgewall.org and bugzilla okay I am trying redming http://demo.redmine.org I registered an account so we can try the demo, login: gsoc_test password: gsoc_test I will try it :) :D ---------------- Lei -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Wed May 27 18:07:56 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 18:07:56 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal Message-ID: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Hello, I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html username: CarlGeorge proposed subject: Community Approved Third Party Repositories proposed location: http://wiki.centos.org/AdditionalResources/CATPR I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? Anyways, please create the article and grant me edit permission to it. Thanks! Carl George IUS CoreDev Team From ajb at elrepo.org Wed May 27 18:27:47 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 19:27:47 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Message-ID: On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR From carl.george at RACKSPACE.COM Wed May 27 21:36:59 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 21:36:59 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com>, Message-ID: <1432762564936.615@RACKSPACE.COM> Thanks Alan. While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? Carl George ________________________________________ From: centos-docs-bounces at centos.org on behalf of Alan Bartlett Sent: Wednesday, May 27, 2015 01:27 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] CATPR - new article for pending proposal On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs From ajb at elrepo.org Wed May 27 21:51:16 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 22:51:16 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <1432762564936.615@RACKSPACE.COM> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> <1432762564936.615@RACKSPACE.COM> Message-ID: On 27 May 2015 at 22:36, Carl George wrote: > Thanks Alan. > > While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? > > Carl George Sure. No problem. Alan. From carl.george at RACKSPACE.COM Thu May 28 23:04:35 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Thu, 28 May 2015 23:04:35 +0000 Subject: [CentOS-docs] proposal for Community Approved Third Party Repos (CATPR) Message-ID: <86aaddfe0e6348c6901a94c5013b4103@544124-OEXCH02.ror-uc.rackspace.com> Howdy, I am proposing a process for 3rd party repositories that would allow them to have their release RPM added the the CentOS Extras repository. http://wiki.centos.org/CarlGeorge/CATPR I would like to start a discussion about approving the proposal and how to move forward. Carl George IUS CoreDev Team From kunaalus at gmail.com Fri May 29 19:33:52 2015 From: kunaalus at gmail.com (kunaal jain) Date: Sat, 30 May 2015 01:03:52 +0530 Subject: [CentOS-docs] Regarding GSoC project Message-ID: 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-development/ Lei made a great chart comparing the platforms. https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing 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 ?? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dougal at dougalmatthews.com Sat May 30 16:19:35 2015 From: dougal at dougalmatthews.com (Dougal Matthews) Date: Sat, 30 May 2015 17:19:35 +0100 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: On 29 May 2015 at 20:33, kunaal jain wrote: > > 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-development/ > > Lei made a great chart comparing the platforms. > > https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing > > 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. As a word of warning here, not all Markdown parsers and renderers are the same. GitHub's makes a number of additions and changes that go against the original (admittedly vague) spec. This could mean your previews are different and may not match the documentation build. An alternative approach would be to build the docs in CI and link to the built version in a comment on both systems. > > Please let us know, what you think about this? > > Regards, > Kunaal > > > -- > Regards, > Kunaal Jain > > > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > From yltt1234512 at gmail.com Sun May 31 04:26:52 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:26:52 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: <745C8184-DCB1-451B-82BB-71AC124E3412@gmail.com> >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Sun May 31 04:37:02 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:37:02 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From silvertip257 at gmail.com Fri May 1 17:17:10 2015 From: silvertip257 at gmail.com (Mike - st257) Date: Fri, 1 May 2015 13:17:10 -0400 Subject: [CentOS-docs] delete account In-Reply-To: References: Message-ID: On Thu, Apr 30, 2015 at 12:31 PM, Carl George wrote: > Hello, > > I goofed and didn't read the contribute page before trying to create my > account on the wiki. I created the first account as "carlgeorge". I then > created a second account in the proper format, "CarlGeorge". Please delete > the first account. > You can change your username after the fact. > > Carl George > Rackspace RPM Development > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Fri May 1 17:36:22 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Fri, 1 May 2015 17:36:22 +0000 Subject: [CentOS-docs] delete account In-Reply-To: References: , Message-ID: <1430501744475.93987@RACKSPACE.COM> I tried that before I created the "CarlGeorge" account. It gave me an error stating that the user already existed (again, this was before I created the "CarlGeorge" account). However, just creating a new account as "CarlGeorge" worked. Please delete the "carlgeorge" account. The email account tied to it is the one I want to use on the "CarlGeorge" account. It won't let me change it. Carl George Rackspace RPM Development ________________________________ From: centos-docs-bounces at centos.org on behalf of Mike - st257 Sent: Friday, May 1, 2015 12:17 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] delete account On Thu, Apr 30, 2015 at 12:31 PM, Carl George > wrote: Hello, I goofed and didn't read the contribute page before trying to create my account on the wiki. I created the first account as "carlgeorge". I then created a second account in the proper format, "CarlGeorge". Please delete the first account. You can change your username after the fact. Carl George Rackspace RPM Development _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From amyagi at gmail.com Fri May 1 17:44:35 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Fri, 1 May 2015 10:44:35 -0700 Subject: [CentOS-docs] delete account In-Reply-To: <1430501744475.93987@RACKSPACE.COM> References: <1430501744475.93987@RACKSPACE.COM> Message-ID: On Fri, May 1, 2015 at 10:36 AM, Carl George wrote: > I tried that before I created the "CarlGeorge" account. It gave me an error > stating that the user already existed (again, this was before I created the > "CarlGeorge" account). However, just creating a new account as "CarlGeorge" > worked. > > Please delete the "carlgeorge" account. The email account tied to it is the > one I want to use on the "CarlGeorge" account. It won't let me change it. Ah, you should have mentioned that earlier. :) I see an account name carl.george. It now has a bogus email and the account is permanently disabled. Please confirm you have no issue with the "CarlGeorge" account. Deleting an account can only be done by administrators of the machine. But it's probably not necessary. Akemi From kwade at redhat.com Thu May 7 08:45:40 2015 From: kwade at redhat.com (Karsten Wade) Date: Thu, 07 May 2015 01:45:40 -0700 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <554B2634.8000808@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to welcome the two Summer of Code students who will be building different parts of the new CentOS documentation toolchain. * Kunal Jain * Lei Yang Students -- welcome again, and thank you for your work this far in helping define the project. Now we have the pleasure of working on the two new scopes that will work interdependently and independently. All of the discussion around this new toolchain has occurred on this mailing list, however the final accepted proposals are behind the GSoC webtool curtain. This is to our advantage, as we need to re-think the project plans across two students. As a refresher, here is the original idea: http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain And some relevant emails & threads: - From here: http://lists.centos.org/pipermail/centos-docs/2015-March/thread.html http://lists.centos.org/pipermail/centos-docs/2015-April/thread.html http://lists.centos.org/pipermail/centos-docs/2015-March/005593.html http://lists.centos.org/pipermail/centos-docs/2015-March/005594.html http://lists.centos.org/pipermail/centos-docs/2015-March/005618.html http://lists.centos.org/pipermail/centos-docs/2015-March/005620.html http://lists.centos.org/pipermail/centos-docs/2015-April/005623.html http://lists.centos.org/pipermail/centos-docs/2015-April/005624.html http://lists.centos.org/pipermail/centos-docs/2015-April/005629.html In discussions with the two students, myself, and Shaun McCance, we determined that we could effectively split up this project. That means the students will need to generate new work plans around individual scopes. These scopes will avoid overlap and interdependence so that each student is able to be successful without the others' project. So now the next fun part begins -- working out two scopes of work, the timing (as Kunaal's and Lei's schedules differ by a bit on either end of the summer), and what needs to be done in what order for all this to work. Cheers, - - 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) iEYEARECAAYFAlVLJjQACgkQ2ZIOBq0ODEEtnQCgsfpu4/EkRyShOKpgOuLZDUDz qO8AoOGTLXIMBWgmd6dg2NW9lR3H42y0 =TgvW -----END PGP SIGNATURE----- From kunaalus at gmail.com Thu May 7 13:14:36 2015 From: kunaalus at gmail.com (kunaal jain) Date: Thu, 7 May 2015 18:44:36 +0530 Subject: [CentOS-docs] Self Introduction [GSoC] Message-ID: Hi guys, I am Kunal Jain from India doing my undergraduate studies in Computer Science from Indian Institute of Technology Guwahati (IITG). I and Lei will be creating a new toolchain that will lower the barrier for contributing new content under the mentor-ship of Karsten this summer. I look forward working with you guys. More details : http://lists.centos.org/pipermail/centos-docs/2015-May/005647.html Regards, Kunal Jain -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Thu May 7 16:37:07 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 8 May 2015 00:37:07 +0800 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <887B9A98-85E9-450B-ADC4-119E14D68682@gmail.com> Thanks Karsten and nice to meet you :) I am looking forward to working with Kunal, Karsten and the community to build a new, easy-to-use docs toolchain for CentOS! I am Lei Yang from China, now studying at School of EECS, Peking University, China. In my original proposal, I think we may build an ?infrastructure?, moving docs between CentOS git repo and github. Then we build useful tools on that infrastructure to enable easier contribution and monitoring, all working with the git repo. I am happy to receive all ideas and suggestions! Thanks in advance! Lei From kbsingh at centos.org Tue May 12 10:13:14 2015 From: kbsingh at centos.org (Karanbir Singh) Date: Tue, 12 May 2015 11:13:14 +0100 Subject: [CentOS-docs] Container Pipeline placeholder Message-ID: <5551D23A.7000501@centos.org> Hi, I've created http://wiki.centos.org/ContainerPipleline as a placeholder to start populating about the pipeline. Although this will run from ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it will form a sort of ecocystem test + release process, I think it deserves scope beyond being just under the CI namespace. - KB -- 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 From lmohanty at redhat.com Tue May 12 10:19:38 2015 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Tue, 12 May 2015 15:49:38 +0530 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5551D3BA.7000307@redhat.com> On 05/12/2015 03:43 PM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. > > - KB > I [1] would like to contribute to the wiki page. So please give me write access. [1] http://wiki.centos.org/LalatenduMohanty Thanks, Lala From mail-lists at karan.org Tue May 12 10:43:59 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Tue, 12 May 2015 11:43:59 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D3BA.7000307@redhat.com> References: <5551D23A.7000501@centos.org> <5551D3BA.7000307@redhat.com> Message-ID: <5551D96F.1020209@karan.org> On 12/05/15 11:19, Lalatendu Mohanty wrote: > On 05/12/2015 03:43 PM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. >> >> - KB >> > > I [1] would like to contribute to the wiki page. So please give me write > access. > > [1] http://wiki.centos.org/LalatenduMohanty > done -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From kwade at redhat.com Wed May 13 05:29:01 2015 From: kwade at redhat.com (Karsten Wade) Date: Tue, 12 May 2015 22:29:01 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel Message-ID: <5552E11D.5030502@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a heads up that we're pulling together a last-hour discussion with the two GSoC students and myself in about 90 minutes in #centos-devel to discuss how the docs toolchain project will shape up - -- split the project, set timelines, and discuss resource needs. We'll post a log after the meeting is done, just wanted to send out a heads up in case anyone is a interesting in joining or lurking. Regards, - - 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) iEYEARECAAYFAlVS4R0ACgkQ2ZIOBq0ODEEAHwCg4R8FWTsAjDNhbqqjngJWoFvN IhsAoNcO8TTe9eBiNPUevqooIfc/V5Z9 =j41w -----END PGP SIGNATURE----- From kwade at redhat.com Wed May 13 13:58:30 2015 From: kwade at redhat.com (Karsten Wade) Date: Wed, 13 May 2015 06:58:30 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel In-Reply-To: <5552E11D.5030502@redhat.com> References: <5552E11D.5030502@redhat.com> Message-ID: <55535886.3010103@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://www.centos.org/minutes/2015/may/centos-devel.2015-05-13-07.08.htm l Minutes summary from above: ====================================== #centos-devel: Docs toolchain planning ====================================== Meeting started by quaid at 07:08:25 UTC. The full logs are available at centos-devel/2015/centos-devel.2015-05-13-07.08.log.html . Meeting summary - --------------- * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (quaid, 07:11:22) * LINK: https://cloud.githubusercontent.com/assets/7388044/6873628/b0b99aa4-d4d7 - -11e4-8aa6-7b25aa69585e.png (kunaaljain, 07:45:40) * LINK: https://docs.docker.com/ (kunaaljain, 07:59:21) * LINK: https://www.digitalocean.com/community/tutorials/?primary_filter=newes t (yangl1996, 08:00:16) * Need to figure out interaction with existing wiki content (refer in, publish to, etc.) (quaid, 08:55:34) * need to define the process and role for accepting changes in to git.centos.org (quaid, 08:56:10) * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (yangl1996, 09:01:53) Meeting ended at 09:31:49 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * yangl1996 (51) * kunaaljain (33) * quaid (31) * Arrfab (15) * centbot (2) * d0ugal (2) * Bahhumbug (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- 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) iEYEARECAAYFAlVTWIYACgkQ2ZIOBq0ODEHZgQCgqXd2VT6flMyFFimc++clW29h UasAn32egD2YC/I1MSejYW2cH2o4TIA1 =XN7+ -----END PGP SIGNATURE----- From jzb at redhat.com Thu May 14 14:35:46 2015 From: jzb at redhat.com (Joe Brockmeier) Date: Thu, 14 May 2015 10:35:46 -0400 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5554B2C2.5030902@redhat.com> On 05/12/2015 06:13 AM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. Pipleline? :-) Should that be: http://wiki.centos.org/ContainerPipeline ? Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From amyagi at gmail.com Thu May 14 14:54:49 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Thu, 14 May 2015 07:54:49 -0700 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5554B2C2.5030902@redhat.com> References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: > On 05/12/2015 06:13 AM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. > > Pipleline? :-) > > Should that be: > > http://wiki.centos.org/ContainerPipeline > > ? Funny that on one noticed. :) http://wiki.centos.org/ContainerPipeline?action=info Akemi From ajb at elrepo.org Thu May 14 15:05:10 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Thu, 14 May 2015 16:05:10 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On 14 May 2015 at 15:54, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info > > Akemi But I have noticed your typo! s/that on one/that no one/ I now claim my prize . . . :P Alan. From mail-lists at karan.org Thu May 14 15:04:22 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Thu, 14 May 2015 16:04:22 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: <5554B976.6070409@karan.org> On 05/14/2015 03:54 PM, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info someone did..! thanks -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From yltt1234512 at gmail.com Fri May 22 14:47:51 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 22 May 2015 22:47:51 +0800 Subject: [CentOS-docs] IRC Log - Kunaal and Lei - New Doc Toolchain - 05/20/2015 Message-ID: Hi! Kunaal and I had an IRC chat last Wednesday at UTC 0600. We discussed about the new docs toolchain. The first part of the chat log is about the workflow, here is the summary: 1. user write on local text editor / on github or a web based editor 2. the PR is created on github, and the info is synced to a reviewing platform, where staff discussed about, tag and accept the file 3. if the PR is accepted, the new article is synced from github to git.centos.org 4. new article is deployed and the doc site is updated 5. a tool convert the new article to different formats for upstream projects to use hey hi! So did u think anything about project I think something about the timeline tell me I think by midterm, we should generally finish half of the reviewing platform and the syncing tool Reviewing platform is definitely a big task yes we can ask on the mailing list for some existing open source project We have one and half month for the mid terms such as some bug tracking platform yes let's see tools required according to workflow First user writes a content Where does he write it? I thought about three ways: 1. he writes on local computer and push it to github 2. he write on a web-based editor 3. he write directly on github do you have other ideas? Sounds good to me. Github uses its own github markdown language So we adapt that? oh it is a problem i have no idea currently although adapting it will make the language more powerful, it is not "standard" markdown We can use that. its almost standard i think sounds good to me adapting this will help us using github tools good idea! about web - based editor. New editor or existing tools I think we can use existing tools, because developing a new editor is a huge task in my mind - if we have time after finishing other parts, we can build one Yeah, if we have left over time, we will do that. good idea! Okay so content is written A pull request has been created on github any other option? yes, totally agreed then what happens next? now that the content is on github, the staff should review it, tag it and comment on it Yes but what happens internally? Tool wise maybe the commit should trigger the syncing tool? there is no commit yet. Just a Pull Request so the commit info is synced to reviewing platform the staff need to review it and comment on it Maybe this pull request creates a issue in review platform yes, exactly what I think This review platform helps in tagging and commenting? yes Sounds good to me. Once the content is tagged and commented. Changes are made. yes, the staff accept the new content Then there should be an option to commit and close. exactly and the pull request can be merged in the repo on github once the commit is made, this is synced to git.c.o yes there involves some communication with github Yes one way sync? I think the communication happens in these situations: 1. github sync commit info to reviewing platform (create a issue on reviewing platfrom) 2. when staff accept the commit on reviewing platfrom, this actions is synced to github 3. the one way sync of repo data from github to git.c.o do you have some ideas? Yes. Also the issue needs to be synced i think yes! because staff comments and suggests changes exactly new changes are made on that pull request on github these changes have to be reflected on our platform so this should be a two-way sync yes I agree with you then 3rd point you made is correct one way sync from github to git.c.o yes once sync is done, Then new site has to be generated and deployed. we can use open source tools to do this Yes that sounds easy. Mkdocs we can use that ;) Then upstream projects :) yes we use pull model here a REST API? sounds good! This will take some time I guess. Totally a new model here I don't think previously it has been implemented yes, we need to build from bottom up I think so a have no idea about how open source projects share docs do they use some special format / conventions? I don't think there is such thing till now. so we have the basic workflow defined now? i think so so in basic tool chain what else we need don't know whether we need other parts do you have some ideas? I think what we discussed covers the basic part yes Content writing -> reviewing -> deployment -> upstream exactly what a doc system needs Yes. here is the ether pad link: http://etherpad.osuosl.org/CentOS-Docs-toolchain let's add the workflow to it Now I think it is very difficult to divide the proposed tools between us so that we can work independently so others can know our idea at once yes, so much dependency between parts Yeah definitely So What do you think? Working independently or together? Is it possible? if we will work in parallel, we need to define a set of APIs mainly between syncing tool and reviewing platform Defining before start is hard I think especially when we don?t know I think so! how reviewing platform will work yes exactly Development of it from scratch is not possible yes i am searching for some open source bug tracking platform Yes. We can modify it but we need the base yes So either we can work parallel and discuss everyday what we are doing, We can share work and problems I totally agree we need to sync our progress frequently maybe this will be of some use: http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems The list is quite big. You have a look at them, I will too ok! and I found centos is now using mantis as bug tracker: http://www.mantisbt.org/demo.php , I will see the features mantis supports centos doesnt use bugzilla? note that mantis is not open source oh! that's bad we need to use open source tools no no it is open source http://www.mantisbt.org/download.php https://github.com/mantisbt/mantisbt yeah! about the reviewing platform how do we implement it Ours requirement is not exactly as bug tracking we need to interact with github at each point i agree with you what we build is a platform syncing data with github realtime I think once we decide on review platform we can divide work and start but we need review platform details first i think yes let's discuss in in detail; yeah what can it do commenting, tagging just like github's issue tracking tool i think yes Exactly it is like bugzilla + github yes! so what we do for this? can we base the platform on bugzilla bugzilla meets our requirements? i think no we need to develop new features what about other platforms? the list you gave we need to integrate with git, so the choice narrows down a bit so the first task is find a reviewing platform can we do this by today so that we can meet up tomorrow or day after tomorrow again discuss the API and changes in platform yes exactly and start working on it ok! Regarding dividing work One option is we work parallel as reviewing platform definitely requries that we both work together yes so we can work together. the only con is we become dependent. We won;t be able to quantify our individual effort. It will like a team. I am okay with it I think I am okay, too Great! So let's hunt a review platform fast. Once we finalise that we will work on timeline and then finally start coding :D ok! I've narrowed down the choice from the list to a few open source projects :D Great. Keep me informed about the same. I will too look at them :) with requirement of supporting git and being open source, there are three choices from the list: http://www.fusionforge.org , http://www.redmine.org , http://trac.edgewall.org and bugzilla okay I am trying redming http://demo.redmine.org I registered an account so we can try the demo, login: gsoc_test password: gsoc_test I will try it :) :D ---------------- Lei -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Wed May 27 18:07:56 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 18:07:56 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal Message-ID: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Hello, I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html username: CarlGeorge proposed subject: Community Approved Third Party Repositories proposed location: http://wiki.centos.org/AdditionalResources/CATPR I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? Anyways, please create the article and grant me edit permission to it. Thanks! Carl George IUS CoreDev Team From ajb at elrepo.org Wed May 27 18:27:47 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 19:27:47 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Message-ID: On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR From carl.george at RACKSPACE.COM Wed May 27 21:36:59 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 21:36:59 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com>, Message-ID: <1432762564936.615@RACKSPACE.COM> Thanks Alan. While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? Carl George ________________________________________ From: centos-docs-bounces at centos.org on behalf of Alan Bartlett Sent: Wednesday, May 27, 2015 01:27 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] CATPR - new article for pending proposal On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs From ajb at elrepo.org Wed May 27 21:51:16 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 22:51:16 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <1432762564936.615@RACKSPACE.COM> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> <1432762564936.615@RACKSPACE.COM> Message-ID: On 27 May 2015 at 22:36, Carl George wrote: > Thanks Alan. > > While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? > > Carl George Sure. No problem. Alan. From carl.george at RACKSPACE.COM Thu May 28 23:04:35 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Thu, 28 May 2015 23:04:35 +0000 Subject: [CentOS-docs] proposal for Community Approved Third Party Repos (CATPR) Message-ID: <86aaddfe0e6348c6901a94c5013b4103@544124-OEXCH02.ror-uc.rackspace.com> Howdy, I am proposing a process for 3rd party repositories that would allow them to have their release RPM added the the CentOS Extras repository. http://wiki.centos.org/CarlGeorge/CATPR I would like to start a discussion about approving the proposal and how to move forward. Carl George IUS CoreDev Team From kunaalus at gmail.com Fri May 29 19:33:52 2015 From: kunaalus at gmail.com (kunaal jain) Date: Sat, 30 May 2015 01:03:52 +0530 Subject: [CentOS-docs] Regarding GSoC project Message-ID: 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-development/ Lei made a great chart comparing the platforms. https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing 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 ?? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dougal at dougalmatthews.com Sat May 30 16:19:35 2015 From: dougal at dougalmatthews.com (Dougal Matthews) Date: Sat, 30 May 2015 17:19:35 +0100 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: On 29 May 2015 at 20:33, kunaal jain wrote: > > 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-development/ > > Lei made a great chart comparing the platforms. > > https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing > > 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. As a word of warning here, not all Markdown parsers and renderers are the same. GitHub's makes a number of additions and changes that go against the original (admittedly vague) spec. This could mean your previews are different and may not match the documentation build. An alternative approach would be to build the docs in CI and link to the built version in a comment on both systems. > > Please let us know, what you think about this? > > Regards, > Kunaal > > > -- > Regards, > Kunaal Jain > > > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > From yltt1234512 at gmail.com Sun May 31 04:26:52 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:26:52 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: <745C8184-DCB1-451B-82BB-71AC124E3412@gmail.com> >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Sun May 31 04:37:02 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:37:02 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From silvertip257 at gmail.com Fri May 1 17:17:10 2015 From: silvertip257 at gmail.com (Mike - st257) Date: Fri, 1 May 2015 13:17:10 -0400 Subject: [CentOS-docs] delete account In-Reply-To: References: Message-ID: On Thu, Apr 30, 2015 at 12:31 PM, Carl George wrote: > Hello, > > I goofed and didn't read the contribute page before trying to create my > account on the wiki. I created the first account as "carlgeorge". I then > created a second account in the proper format, "CarlGeorge". Please delete > the first account. > You can change your username after the fact. > > Carl George > Rackspace RPM Development > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Fri May 1 17:36:22 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Fri, 1 May 2015 17:36:22 +0000 Subject: [CentOS-docs] delete account In-Reply-To: References: , Message-ID: <1430501744475.93987@RACKSPACE.COM> I tried that before I created the "CarlGeorge" account. It gave me an error stating that the user already existed (again, this was before I created the "CarlGeorge" account). However, just creating a new account as "CarlGeorge" worked. Please delete the "carlgeorge" account. The email account tied to it is the one I want to use on the "CarlGeorge" account. It won't let me change it. Carl George Rackspace RPM Development ________________________________ From: centos-docs-bounces at centos.org on behalf of Mike - st257 Sent: Friday, May 1, 2015 12:17 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] delete account On Thu, Apr 30, 2015 at 12:31 PM, Carl George > wrote: Hello, I goofed and didn't read the contribute page before trying to create my account on the wiki. I created the first account as "carlgeorge". I then created a second account in the proper format, "CarlGeorge". Please delete the first account. You can change your username after the fact. Carl George Rackspace RPM Development _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From amyagi at gmail.com Fri May 1 17:44:35 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Fri, 1 May 2015 10:44:35 -0700 Subject: [CentOS-docs] delete account In-Reply-To: <1430501744475.93987@RACKSPACE.COM> References: <1430501744475.93987@RACKSPACE.COM> Message-ID: On Fri, May 1, 2015 at 10:36 AM, Carl George wrote: > I tried that before I created the "CarlGeorge" account. It gave me an error > stating that the user already existed (again, this was before I created the > "CarlGeorge" account). However, just creating a new account as "CarlGeorge" > worked. > > Please delete the "carlgeorge" account. The email account tied to it is the > one I want to use on the "CarlGeorge" account. It won't let me change it. Ah, you should have mentioned that earlier. :) I see an account name carl.george. It now has a bogus email and the account is permanently disabled. Please confirm you have no issue with the "CarlGeorge" account. Deleting an account can only be done by administrators of the machine. But it's probably not necessary. Akemi From kwade at redhat.com Thu May 7 08:45:40 2015 From: kwade at redhat.com (Karsten Wade) Date: Thu, 07 May 2015 01:45:40 -0700 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <554B2634.8000808@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to welcome the two Summer of Code students who will be building different parts of the new CentOS documentation toolchain. * Kunal Jain * Lei Yang Students -- welcome again, and thank you for your work this far in helping define the project. Now we have the pleasure of working on the two new scopes that will work interdependently and independently. All of the discussion around this new toolchain has occurred on this mailing list, however the final accepted proposals are behind the GSoC webtool curtain. This is to our advantage, as we need to re-think the project plans across two students. As a refresher, here is the original idea: http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain And some relevant emails & threads: - From here: http://lists.centos.org/pipermail/centos-docs/2015-March/thread.html http://lists.centos.org/pipermail/centos-docs/2015-April/thread.html http://lists.centos.org/pipermail/centos-docs/2015-March/005593.html http://lists.centos.org/pipermail/centos-docs/2015-March/005594.html http://lists.centos.org/pipermail/centos-docs/2015-March/005618.html http://lists.centos.org/pipermail/centos-docs/2015-March/005620.html http://lists.centos.org/pipermail/centos-docs/2015-April/005623.html http://lists.centos.org/pipermail/centos-docs/2015-April/005624.html http://lists.centos.org/pipermail/centos-docs/2015-April/005629.html In discussions with the two students, myself, and Shaun McCance, we determined that we could effectively split up this project. That means the students will need to generate new work plans around individual scopes. These scopes will avoid overlap and interdependence so that each student is able to be successful without the others' project. So now the next fun part begins -- working out two scopes of work, the timing (as Kunaal's and Lei's schedules differ by a bit on either end of the summer), and what needs to be done in what order for all this to work. Cheers, - - 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) iEYEARECAAYFAlVLJjQACgkQ2ZIOBq0ODEEtnQCgsfpu4/EkRyShOKpgOuLZDUDz qO8AoOGTLXIMBWgmd6dg2NW9lR3H42y0 =TgvW -----END PGP SIGNATURE----- From kunaalus at gmail.com Thu May 7 13:14:36 2015 From: kunaalus at gmail.com (kunaal jain) Date: Thu, 7 May 2015 18:44:36 +0530 Subject: [CentOS-docs] Self Introduction [GSoC] Message-ID: Hi guys, I am Kunal Jain from India doing my undergraduate studies in Computer Science from Indian Institute of Technology Guwahati (IITG). I and Lei will be creating a new toolchain that will lower the barrier for contributing new content under the mentor-ship of Karsten this summer. I look forward working with you guys. More details : http://lists.centos.org/pipermail/centos-docs/2015-May/005647.html Regards, Kunal Jain -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Thu May 7 16:37:07 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 8 May 2015 00:37:07 +0800 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <887B9A98-85E9-450B-ADC4-119E14D68682@gmail.com> Thanks Karsten and nice to meet you :) I am looking forward to working with Kunal, Karsten and the community to build a new, easy-to-use docs toolchain for CentOS! I am Lei Yang from China, now studying at School of EECS, Peking University, China. In my original proposal, I think we may build an ?infrastructure?, moving docs between CentOS git repo and github. Then we build useful tools on that infrastructure to enable easier contribution and monitoring, all working with the git repo. I am happy to receive all ideas and suggestions! Thanks in advance! Lei From kbsingh at centos.org Tue May 12 10:13:14 2015 From: kbsingh at centos.org (Karanbir Singh) Date: Tue, 12 May 2015 11:13:14 +0100 Subject: [CentOS-docs] Container Pipeline placeholder Message-ID: <5551D23A.7000501@centos.org> Hi, I've created http://wiki.centos.org/ContainerPipleline as a placeholder to start populating about the pipeline. Although this will run from ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it will form a sort of ecocystem test + release process, I think it deserves scope beyond being just under the CI namespace. - KB -- 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 From lmohanty at redhat.com Tue May 12 10:19:38 2015 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Tue, 12 May 2015 15:49:38 +0530 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5551D3BA.7000307@redhat.com> On 05/12/2015 03:43 PM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. > > - KB > I [1] would like to contribute to the wiki page. So please give me write access. [1] http://wiki.centos.org/LalatenduMohanty Thanks, Lala From mail-lists at karan.org Tue May 12 10:43:59 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Tue, 12 May 2015 11:43:59 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D3BA.7000307@redhat.com> References: <5551D23A.7000501@centos.org> <5551D3BA.7000307@redhat.com> Message-ID: <5551D96F.1020209@karan.org> On 12/05/15 11:19, Lalatendu Mohanty wrote: > On 05/12/2015 03:43 PM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. >> >> - KB >> > > I [1] would like to contribute to the wiki page. So please give me write > access. > > [1] http://wiki.centos.org/LalatenduMohanty > done -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From kwade at redhat.com Wed May 13 05:29:01 2015 From: kwade at redhat.com (Karsten Wade) Date: Tue, 12 May 2015 22:29:01 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel Message-ID: <5552E11D.5030502@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a heads up that we're pulling together a last-hour discussion with the two GSoC students and myself in about 90 minutes in #centos-devel to discuss how the docs toolchain project will shape up - -- split the project, set timelines, and discuss resource needs. We'll post a log after the meeting is done, just wanted to send out a heads up in case anyone is a interesting in joining or lurking. Regards, - - 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) iEYEARECAAYFAlVS4R0ACgkQ2ZIOBq0ODEEAHwCg4R8FWTsAjDNhbqqjngJWoFvN IhsAoNcO8TTe9eBiNPUevqooIfc/V5Z9 =j41w -----END PGP SIGNATURE----- From kwade at redhat.com Wed May 13 13:58:30 2015 From: kwade at redhat.com (Karsten Wade) Date: Wed, 13 May 2015 06:58:30 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel In-Reply-To: <5552E11D.5030502@redhat.com> References: <5552E11D.5030502@redhat.com> Message-ID: <55535886.3010103@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://www.centos.org/minutes/2015/may/centos-devel.2015-05-13-07.08.htm l Minutes summary from above: ====================================== #centos-devel: Docs toolchain planning ====================================== Meeting started by quaid at 07:08:25 UTC. The full logs are available at centos-devel/2015/centos-devel.2015-05-13-07.08.log.html . Meeting summary - --------------- * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (quaid, 07:11:22) * LINK: https://cloud.githubusercontent.com/assets/7388044/6873628/b0b99aa4-d4d7 - -11e4-8aa6-7b25aa69585e.png (kunaaljain, 07:45:40) * LINK: https://docs.docker.com/ (kunaaljain, 07:59:21) * LINK: https://www.digitalocean.com/community/tutorials/?primary_filter=newes t (yangl1996, 08:00:16) * Need to figure out interaction with existing wiki content (refer in, publish to, etc.) (quaid, 08:55:34) * need to define the process and role for accepting changes in to git.centos.org (quaid, 08:56:10) * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (yangl1996, 09:01:53) Meeting ended at 09:31:49 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * yangl1996 (51) * kunaaljain (33) * quaid (31) * Arrfab (15) * centbot (2) * d0ugal (2) * Bahhumbug (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- 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) iEYEARECAAYFAlVTWIYACgkQ2ZIOBq0ODEHZgQCgqXd2VT6flMyFFimc++clW29h UasAn32egD2YC/I1MSejYW2cH2o4TIA1 =XN7+ -----END PGP SIGNATURE----- From jzb at redhat.com Thu May 14 14:35:46 2015 From: jzb at redhat.com (Joe Brockmeier) Date: Thu, 14 May 2015 10:35:46 -0400 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5554B2C2.5030902@redhat.com> On 05/12/2015 06:13 AM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. Pipleline? :-) Should that be: http://wiki.centos.org/ContainerPipeline ? Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From amyagi at gmail.com Thu May 14 14:54:49 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Thu, 14 May 2015 07:54:49 -0700 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5554B2C2.5030902@redhat.com> References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: > On 05/12/2015 06:13 AM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. > > Pipleline? :-) > > Should that be: > > http://wiki.centos.org/ContainerPipeline > > ? Funny that on one noticed. :) http://wiki.centos.org/ContainerPipeline?action=info Akemi From ajb at elrepo.org Thu May 14 15:05:10 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Thu, 14 May 2015 16:05:10 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On 14 May 2015 at 15:54, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info > > Akemi But I have noticed your typo! s/that on one/that no one/ I now claim my prize . . . :P Alan. From mail-lists at karan.org Thu May 14 15:04:22 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Thu, 14 May 2015 16:04:22 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: <5554B976.6070409@karan.org> On 05/14/2015 03:54 PM, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info someone did..! thanks -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From yltt1234512 at gmail.com Fri May 22 14:47:51 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 22 May 2015 22:47:51 +0800 Subject: [CentOS-docs] IRC Log - Kunaal and Lei - New Doc Toolchain - 05/20/2015 Message-ID: Hi! Kunaal and I had an IRC chat last Wednesday at UTC 0600. We discussed about the new docs toolchain. The first part of the chat log is about the workflow, here is the summary: 1. user write on local text editor / on github or a web based editor 2. the PR is created on github, and the info is synced to a reviewing platform, where staff discussed about, tag and accept the file 3. if the PR is accepted, the new article is synced from github to git.centos.org 4. new article is deployed and the doc site is updated 5. a tool convert the new article to different formats for upstream projects to use hey hi! So did u think anything about project I think something about the timeline tell me I think by midterm, we should generally finish half of the reviewing platform and the syncing tool Reviewing platform is definitely a big task yes we can ask on the mailing list for some existing open source project We have one and half month for the mid terms such as some bug tracking platform yes let's see tools required according to workflow First user writes a content Where does he write it? I thought about three ways: 1. he writes on local computer and push it to github 2. he write on a web-based editor 3. he write directly on github do you have other ideas? Sounds good to me. Github uses its own github markdown language So we adapt that? oh it is a problem i have no idea currently although adapting it will make the language more powerful, it is not "standard" markdown We can use that. its almost standard i think sounds good to me adapting this will help us using github tools good idea! about web - based editor. New editor or existing tools I think we can use existing tools, because developing a new editor is a huge task in my mind - if we have time after finishing other parts, we can build one Yeah, if we have left over time, we will do that. good idea! Okay so content is written A pull request has been created on github any other option? yes, totally agreed then what happens next? now that the content is on github, the staff should review it, tag it and comment on it Yes but what happens internally? Tool wise maybe the commit should trigger the syncing tool? there is no commit yet. Just a Pull Request so the commit info is synced to reviewing platform the staff need to review it and comment on it Maybe this pull request creates a issue in review platform yes, exactly what I think This review platform helps in tagging and commenting? yes Sounds good to me. Once the content is tagged and commented. Changes are made. yes, the staff accept the new content Then there should be an option to commit and close. exactly and the pull request can be merged in the repo on github once the commit is made, this is synced to git.c.o yes there involves some communication with github Yes one way sync? I think the communication happens in these situations: 1. github sync commit info to reviewing platform (create a issue on reviewing platfrom) 2. when staff accept the commit on reviewing platfrom, this actions is synced to github 3. the one way sync of repo data from github to git.c.o do you have some ideas? Yes. Also the issue needs to be synced i think yes! because staff comments and suggests changes exactly new changes are made on that pull request on github these changes have to be reflected on our platform so this should be a two-way sync yes I agree with you then 3rd point you made is correct one way sync from github to git.c.o yes once sync is done, Then new site has to be generated and deployed. we can use open source tools to do this Yes that sounds easy. Mkdocs we can use that ;) Then upstream projects :) yes we use pull model here a REST API? sounds good! This will take some time I guess. Totally a new model here I don't think previously it has been implemented yes, we need to build from bottom up I think so a have no idea about how open source projects share docs do they use some special format / conventions? I don't think there is such thing till now. so we have the basic workflow defined now? i think so so in basic tool chain what else we need don't know whether we need other parts do you have some ideas? I think what we discussed covers the basic part yes Content writing -> reviewing -> deployment -> upstream exactly what a doc system needs Yes. here is the ether pad link: http://etherpad.osuosl.org/CentOS-Docs-toolchain let's add the workflow to it Now I think it is very difficult to divide the proposed tools between us so that we can work independently so others can know our idea at once yes, so much dependency between parts Yeah definitely So What do you think? Working independently or together? Is it possible? if we will work in parallel, we need to define a set of APIs mainly between syncing tool and reviewing platform Defining before start is hard I think especially when we don?t know I think so! how reviewing platform will work yes exactly Development of it from scratch is not possible yes i am searching for some open source bug tracking platform Yes. We can modify it but we need the base yes So either we can work parallel and discuss everyday what we are doing, We can share work and problems I totally agree we need to sync our progress frequently maybe this will be of some use: http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems The list is quite big. You have a look at them, I will too ok! and I found centos is now using mantis as bug tracker: http://www.mantisbt.org/demo.php , I will see the features mantis supports centos doesnt use bugzilla? note that mantis is not open source oh! that's bad we need to use open source tools no no it is open source http://www.mantisbt.org/download.php https://github.com/mantisbt/mantisbt yeah! about the reviewing platform how do we implement it Ours requirement is not exactly as bug tracking we need to interact with github at each point i agree with you what we build is a platform syncing data with github realtime I think once we decide on review platform we can divide work and start but we need review platform details first i think yes let's discuss in in detail; yeah what can it do commenting, tagging just like github's issue tracking tool i think yes Exactly it is like bugzilla + github yes! so what we do for this? can we base the platform on bugzilla bugzilla meets our requirements? i think no we need to develop new features what about other platforms? the list you gave we need to integrate with git, so the choice narrows down a bit so the first task is find a reviewing platform can we do this by today so that we can meet up tomorrow or day after tomorrow again discuss the API and changes in platform yes exactly and start working on it ok! Regarding dividing work One option is we work parallel as reviewing platform definitely requries that we both work together yes so we can work together. the only con is we become dependent. We won;t be able to quantify our individual effort. It will like a team. I am okay with it I think I am okay, too Great! So let's hunt a review platform fast. Once we finalise that we will work on timeline and then finally start coding :D ok! I've narrowed down the choice from the list to a few open source projects :D Great. Keep me informed about the same. I will too look at them :) with requirement of supporting git and being open source, there are three choices from the list: http://www.fusionforge.org , http://www.redmine.org , http://trac.edgewall.org and bugzilla okay I am trying redming http://demo.redmine.org I registered an account so we can try the demo, login: gsoc_test password: gsoc_test I will try it :) :D ---------------- Lei -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Wed May 27 18:07:56 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 18:07:56 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal Message-ID: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Hello, I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html username: CarlGeorge proposed subject: Community Approved Third Party Repositories proposed location: http://wiki.centos.org/AdditionalResources/CATPR I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? Anyways, please create the article and grant me edit permission to it. Thanks! Carl George IUS CoreDev Team From ajb at elrepo.org Wed May 27 18:27:47 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 19:27:47 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Message-ID: On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR From carl.george at RACKSPACE.COM Wed May 27 21:36:59 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 21:36:59 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com>, Message-ID: <1432762564936.615@RACKSPACE.COM> Thanks Alan. While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? Carl George ________________________________________ From: centos-docs-bounces at centos.org on behalf of Alan Bartlett Sent: Wednesday, May 27, 2015 01:27 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] CATPR - new article for pending proposal On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs From ajb at elrepo.org Wed May 27 21:51:16 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 22:51:16 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <1432762564936.615@RACKSPACE.COM> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> <1432762564936.615@RACKSPACE.COM> Message-ID: On 27 May 2015 at 22:36, Carl George wrote: > Thanks Alan. > > While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? > > Carl George Sure. No problem. Alan. From carl.george at RACKSPACE.COM Thu May 28 23:04:35 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Thu, 28 May 2015 23:04:35 +0000 Subject: [CentOS-docs] proposal for Community Approved Third Party Repos (CATPR) Message-ID: <86aaddfe0e6348c6901a94c5013b4103@544124-OEXCH02.ror-uc.rackspace.com> Howdy, I am proposing a process for 3rd party repositories that would allow them to have their release RPM added the the CentOS Extras repository. http://wiki.centos.org/CarlGeorge/CATPR I would like to start a discussion about approving the proposal and how to move forward. Carl George IUS CoreDev Team From kunaalus at gmail.com Fri May 29 19:33:52 2015 From: kunaalus at gmail.com (kunaal jain) Date: Sat, 30 May 2015 01:03:52 +0530 Subject: [CentOS-docs] Regarding GSoC project Message-ID: 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-development/ Lei made a great chart comparing the platforms. https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing 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 ?? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dougal at dougalmatthews.com Sat May 30 16:19:35 2015 From: dougal at dougalmatthews.com (Dougal Matthews) Date: Sat, 30 May 2015 17:19:35 +0100 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: On 29 May 2015 at 20:33, kunaal jain wrote: > > 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-development/ > > Lei made a great chart comparing the platforms. > > https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing > > 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. As a word of warning here, not all Markdown parsers and renderers are the same. GitHub's makes a number of additions and changes that go against the original (admittedly vague) spec. This could mean your previews are different and may not match the documentation build. An alternative approach would be to build the docs in CI and link to the built version in a comment on both systems. > > Please let us know, what you think about this? > > Regards, > Kunaal > > > -- > Regards, > Kunaal Jain > > > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > From yltt1234512 at gmail.com Sun May 31 04:26:52 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:26:52 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: <745C8184-DCB1-451B-82BB-71AC124E3412@gmail.com> >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Sun May 31 04:37:02 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:37:02 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From silvertip257 at gmail.com Fri May 1 17:17:10 2015 From: silvertip257 at gmail.com (Mike - st257) Date: Fri, 1 May 2015 13:17:10 -0400 Subject: [CentOS-docs] delete account In-Reply-To: References: Message-ID: On Thu, Apr 30, 2015 at 12:31 PM, Carl George wrote: > Hello, > > I goofed and didn't read the contribute page before trying to create my > account on the wiki. I created the first account as "carlgeorge". I then > created a second account in the proper format, "CarlGeorge". Please delete > the first account. > You can change your username after the fact. > > Carl George > Rackspace RPM Development > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Fri May 1 17:36:22 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Fri, 1 May 2015 17:36:22 +0000 Subject: [CentOS-docs] delete account In-Reply-To: References: , Message-ID: <1430501744475.93987@RACKSPACE.COM> I tried that before I created the "CarlGeorge" account. It gave me an error stating that the user already existed (again, this was before I created the "CarlGeorge" account). However, just creating a new account as "CarlGeorge" worked. Please delete the "carlgeorge" account. The email account tied to it is the one I want to use on the "CarlGeorge" account. It won't let me change it. Carl George Rackspace RPM Development ________________________________ From: centos-docs-bounces at centos.org on behalf of Mike - st257 Sent: Friday, May 1, 2015 12:17 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] delete account On Thu, Apr 30, 2015 at 12:31 PM, Carl George > wrote: Hello, I goofed and didn't read the contribute page before trying to create my account on the wiki. I created the first account as "carlgeorge". I then created a second account in the proper format, "CarlGeorge". Please delete the first account. You can change your username after the fact. Carl George Rackspace RPM Development _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From amyagi at gmail.com Fri May 1 17:44:35 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Fri, 1 May 2015 10:44:35 -0700 Subject: [CentOS-docs] delete account In-Reply-To: <1430501744475.93987@RACKSPACE.COM> References: <1430501744475.93987@RACKSPACE.COM> Message-ID: On Fri, May 1, 2015 at 10:36 AM, Carl George wrote: > I tried that before I created the "CarlGeorge" account. It gave me an error > stating that the user already existed (again, this was before I created the > "CarlGeorge" account). However, just creating a new account as "CarlGeorge" > worked. > > Please delete the "carlgeorge" account. The email account tied to it is the > one I want to use on the "CarlGeorge" account. It won't let me change it. Ah, you should have mentioned that earlier. :) I see an account name carl.george. It now has a bogus email and the account is permanently disabled. Please confirm you have no issue with the "CarlGeorge" account. Deleting an account can only be done by administrators of the machine. But it's probably not necessary. Akemi From kwade at redhat.com Thu May 7 08:45:40 2015 From: kwade at redhat.com (Karsten Wade) Date: Thu, 07 May 2015 01:45:40 -0700 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <554B2634.8000808@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to welcome the two Summer of Code students who will be building different parts of the new CentOS documentation toolchain. * Kunal Jain * Lei Yang Students -- welcome again, and thank you for your work this far in helping define the project. Now we have the pleasure of working on the two new scopes that will work interdependently and independently. All of the discussion around this new toolchain has occurred on this mailing list, however the final accepted proposals are behind the GSoC webtool curtain. This is to our advantage, as we need to re-think the project plans across two students. As a refresher, here is the original idea: http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain And some relevant emails & threads: - From here: http://lists.centos.org/pipermail/centos-docs/2015-March/thread.html http://lists.centos.org/pipermail/centos-docs/2015-April/thread.html http://lists.centos.org/pipermail/centos-docs/2015-March/005593.html http://lists.centos.org/pipermail/centos-docs/2015-March/005594.html http://lists.centos.org/pipermail/centos-docs/2015-March/005618.html http://lists.centos.org/pipermail/centos-docs/2015-March/005620.html http://lists.centos.org/pipermail/centos-docs/2015-April/005623.html http://lists.centos.org/pipermail/centos-docs/2015-April/005624.html http://lists.centos.org/pipermail/centos-docs/2015-April/005629.html In discussions with the two students, myself, and Shaun McCance, we determined that we could effectively split up this project. That means the students will need to generate new work plans around individual scopes. These scopes will avoid overlap and interdependence so that each student is able to be successful without the others' project. So now the next fun part begins -- working out two scopes of work, the timing (as Kunaal's and Lei's schedules differ by a bit on either end of the summer), and what needs to be done in what order for all this to work. Cheers, - - 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) iEYEARECAAYFAlVLJjQACgkQ2ZIOBq0ODEEtnQCgsfpu4/EkRyShOKpgOuLZDUDz qO8AoOGTLXIMBWgmd6dg2NW9lR3H42y0 =TgvW -----END PGP SIGNATURE----- From kunaalus at gmail.com Thu May 7 13:14:36 2015 From: kunaalus at gmail.com (kunaal jain) Date: Thu, 7 May 2015 18:44:36 +0530 Subject: [CentOS-docs] Self Introduction [GSoC] Message-ID: Hi guys, I am Kunal Jain from India doing my undergraduate studies in Computer Science from Indian Institute of Technology Guwahati (IITG). I and Lei will be creating a new toolchain that will lower the barrier for contributing new content under the mentor-ship of Karsten this summer. I look forward working with you guys. More details : http://lists.centos.org/pipermail/centos-docs/2015-May/005647.html Regards, Kunal Jain -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Thu May 7 16:37:07 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 8 May 2015 00:37:07 +0800 Subject: [CentOS-docs] Welcome GSoC students, getting started Message-ID: <887B9A98-85E9-450B-ADC4-119E14D68682@gmail.com> Thanks Karsten and nice to meet you :) I am looking forward to working with Kunal, Karsten and the community to build a new, easy-to-use docs toolchain for CentOS! I am Lei Yang from China, now studying at School of EECS, Peking University, China. In my original proposal, I think we may build an ?infrastructure?, moving docs between CentOS git repo and github. Then we build useful tools on that infrastructure to enable easier contribution and monitoring, all working with the git repo. I am happy to receive all ideas and suggestions! Thanks in advance! Lei From kbsingh at centos.org Tue May 12 10:13:14 2015 From: kbsingh at centos.org (Karanbir Singh) Date: Tue, 12 May 2015 11:13:14 +0100 Subject: [CentOS-docs] Container Pipeline placeholder Message-ID: <5551D23A.7000501@centos.org> Hi, I've created http://wiki.centos.org/ContainerPipleline as a placeholder to start populating about the pipeline. Although this will run from ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it will form a sort of ecocystem test + release process, I think it deserves scope beyond being just under the CI namespace. - KB -- 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 From lmohanty at redhat.com Tue May 12 10:19:38 2015 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Tue, 12 May 2015 15:49:38 +0530 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5551D3BA.7000307@redhat.com> On 05/12/2015 03:43 PM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. > > - KB > I [1] would like to contribute to the wiki page. So please give me write access. [1] http://wiki.centos.org/LalatenduMohanty Thanks, Lala From mail-lists at karan.org Tue May 12 10:43:59 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Tue, 12 May 2015 11:43:59 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D3BA.7000307@redhat.com> References: <5551D23A.7000501@centos.org> <5551D3BA.7000307@redhat.com> Message-ID: <5551D96F.1020209@karan.org> On 12/05/15 11:19, Lalatendu Mohanty wrote: > On 05/12/2015 03:43 PM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. >> >> - KB >> > > I [1] would like to contribute to the wiki page. So please give me write > access. > > [1] http://wiki.centos.org/LalatenduMohanty > done -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From kwade at redhat.com Wed May 13 05:29:01 2015 From: kwade at redhat.com (Karsten Wade) Date: Tue, 12 May 2015 22:29:01 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel Message-ID: <5552E11D.5030502@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a heads up that we're pulling together a last-hour discussion with the two GSoC students and myself in about 90 minutes in #centos-devel to discuss how the docs toolchain project will shape up - -- split the project, set timelines, and discuss resource needs. We'll post a log after the meeting is done, just wanted to send out a heads up in case anyone is a interesting in joining or lurking. Regards, - - 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) iEYEARECAAYFAlVS4R0ACgkQ2ZIOBq0ODEEAHwCg4R8FWTsAjDNhbqqjngJWoFvN IhsAoNcO8TTe9eBiNPUevqooIfc/V5Z9 =j41w -----END PGP SIGNATURE----- From kwade at redhat.com Wed May 13 13:58:30 2015 From: kwade at redhat.com (Karsten Wade) Date: Wed, 13 May 2015 06:58:30 -0700 Subject: [CentOS-docs] Toolchain discussion 07:00 UTC 13 May in #centos-devel In-Reply-To: <5552E11D.5030502@redhat.com> References: <5552E11D.5030502@redhat.com> Message-ID: <55535886.3010103@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://www.centos.org/minutes/2015/may/centos-devel.2015-05-13-07.08.htm l Minutes summary from above: ====================================== #centos-devel: Docs toolchain planning ====================================== Meeting started by quaid at 07:08:25 UTC. The full logs are available at centos-devel/2015/centos-devel.2015-05-13-07.08.log.html . Meeting summary - --------------- * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (quaid, 07:11:22) * LINK: https://cloud.githubusercontent.com/assets/7388044/6873628/b0b99aa4-d4d7 - -11e4-8aa6-7b25aa69585e.png (kunaaljain, 07:45:40) * LINK: https://docs.docker.com/ (kunaaljain, 07:59:21) * LINK: https://www.digitalocean.com/community/tutorials/?primary_filter=newes t (yangl1996, 08:00:16) * Need to figure out interaction with existing wiki content (refer in, publish to, etc.) (quaid, 08:55:34) * need to define the process and role for accepting changes in to git.centos.org (quaid, 08:56:10) * LINK: http://etherpad.osuosl.org/CentOS-Docs-toolchain (yangl1996, 09:01:53) Meeting ended at 09:31:49 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * yangl1996 (51) * kunaaljain (33) * quaid (31) * Arrfab (15) * centbot (2) * d0ugal (2) * Bahhumbug (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- 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) iEYEARECAAYFAlVTWIYACgkQ2ZIOBq0ODEHZgQCgqXd2VT6flMyFFimc++clW29h UasAn32egD2YC/I1MSejYW2cH2o4TIA1 =XN7+ -----END PGP SIGNATURE----- From jzb at redhat.com Thu May 14 14:35:46 2015 From: jzb at redhat.com (Joe Brockmeier) Date: Thu, 14 May 2015 10:35:46 -0400 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5551D23A.7000501@centos.org> References: <5551D23A.7000501@centos.org> Message-ID: <5554B2C2.5030902@redhat.com> On 05/12/2015 06:13 AM, Karanbir Singh wrote: > Hi, > > I've created http://wiki.centos.org/ContainerPipleline as a placeholder > to start populating about the pipeline. Although this will run from > ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. Pipleline? :-) Should that be: http://wiki.centos.org/ContainerPipeline ? Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From amyagi at gmail.com Thu May 14 14:54:49 2015 From: amyagi at gmail.com (Akemi Yagi) Date: Thu, 14 May 2015 07:54:49 -0700 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: <5554B2C2.5030902@redhat.com> References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: > On 05/12/2015 06:13 AM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >> will form a sort of ecocystem test + release process, I think it >> deserves scope beyond being just under the CI namespace. > > Pipleline? :-) > > Should that be: > > http://wiki.centos.org/ContainerPipeline > > ? Funny that on one noticed. :) http://wiki.centos.org/ContainerPipeline?action=info Akemi From ajb at elrepo.org Thu May 14 15:05:10 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Thu, 14 May 2015 16:05:10 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: On 14 May 2015 at 15:54, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info > > Akemi But I have noticed your typo! s/that on one/that no one/ I now claim my prize . . . :P Alan. From mail-lists at karan.org Thu May 14 15:04:22 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Thu, 14 May 2015 16:04:22 +0100 Subject: [CentOS-docs] Container Pipeline placeholder In-Reply-To: References: <5551D23A.7000501@centos.org> <5554B2C2.5030902@redhat.com> Message-ID: <5554B976.6070409@karan.org> On 05/14/2015 03:54 PM, Akemi Yagi wrote: > On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier wrote: >> On 05/12/2015 06:13 AM, Karanbir Singh wrote: >>> Hi, >>> >>> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >>> to start populating about the pipeline. Although this will run from >>> ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it >>> will form a sort of ecocystem test + release process, I think it >>> deserves scope beyond being just under the CI namespace. >> >> Pipleline? :-) >> >> Should that be: >> >> http://wiki.centos.org/ContainerPipeline >> >> ? > > Funny that on one noticed. :) > > http://wiki.centos.org/ContainerPipeline?action=info someone did..! thanks -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From yltt1234512 at gmail.com Fri May 22 14:47:51 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Fri, 22 May 2015 22:47:51 +0800 Subject: [CentOS-docs] IRC Log - Kunaal and Lei - New Doc Toolchain - 05/20/2015 Message-ID: Hi! Kunaal and I had an IRC chat last Wednesday at UTC 0600. We discussed about the new docs toolchain. The first part of the chat log is about the workflow, here is the summary: 1. user write on local text editor / on github or a web based editor 2. the PR is created on github, and the info is synced to a reviewing platform, where staff discussed about, tag and accept the file 3. if the PR is accepted, the new article is synced from github to git.centos.org 4. new article is deployed and the doc site is updated 5. a tool convert the new article to different formats for upstream projects to use hey hi! So did u think anything about project I think something about the timeline tell me I think by midterm, we should generally finish half of the reviewing platform and the syncing tool Reviewing platform is definitely a big task yes we can ask on the mailing list for some existing open source project We have one and half month for the mid terms such as some bug tracking platform yes let's see tools required according to workflow First user writes a content Where does he write it? I thought about three ways: 1. he writes on local computer and push it to github 2. he write on a web-based editor 3. he write directly on github do you have other ideas? Sounds good to me. Github uses its own github markdown language So we adapt that? oh it is a problem i have no idea currently although adapting it will make the language more powerful, it is not "standard" markdown We can use that. its almost standard i think sounds good to me adapting this will help us using github tools good idea! about web - based editor. New editor or existing tools I think we can use existing tools, because developing a new editor is a huge task in my mind - if we have time after finishing other parts, we can build one Yeah, if we have left over time, we will do that. good idea! Okay so content is written A pull request has been created on github any other option? yes, totally agreed then what happens next? now that the content is on github, the staff should review it, tag it and comment on it Yes but what happens internally? Tool wise maybe the commit should trigger the syncing tool? there is no commit yet. Just a Pull Request so the commit info is synced to reviewing platform the staff need to review it and comment on it Maybe this pull request creates a issue in review platform yes, exactly what I think This review platform helps in tagging and commenting? yes Sounds good to me. Once the content is tagged and commented. Changes are made. yes, the staff accept the new content Then there should be an option to commit and close. exactly and the pull request can be merged in the repo on github once the commit is made, this is synced to git.c.o yes there involves some communication with github Yes one way sync? I think the communication happens in these situations: 1. github sync commit info to reviewing platform (create a issue on reviewing platfrom) 2. when staff accept the commit on reviewing platfrom, this actions is synced to github 3. the one way sync of repo data from github to git.c.o do you have some ideas? Yes. Also the issue needs to be synced i think yes! because staff comments and suggests changes exactly new changes are made on that pull request on github these changes have to be reflected on our platform so this should be a two-way sync yes I agree with you then 3rd point you made is correct one way sync from github to git.c.o yes once sync is done, Then new site has to be generated and deployed. we can use open source tools to do this Yes that sounds easy. Mkdocs we can use that ;) Then upstream projects :) yes we use pull model here a REST API? sounds good! This will take some time I guess. Totally a new model here I don't think previously it has been implemented yes, we need to build from bottom up I think so a have no idea about how open source projects share docs do they use some special format / conventions? I don't think there is such thing till now. so we have the basic workflow defined now? i think so so in basic tool chain what else we need don't know whether we need other parts do you have some ideas? I think what we discussed covers the basic part yes Content writing -> reviewing -> deployment -> upstream exactly what a doc system needs Yes. here is the ether pad link: http://etherpad.osuosl.org/CentOS-Docs-toolchain let's add the workflow to it Now I think it is very difficult to divide the proposed tools between us so that we can work independently so others can know our idea at once yes, so much dependency between parts Yeah definitely So What do you think? Working independently or together? Is it possible? if we will work in parallel, we need to define a set of APIs mainly between syncing tool and reviewing platform Defining before start is hard I think especially when we don?t know I think so! how reviewing platform will work yes exactly Development of it from scratch is not possible yes i am searching for some open source bug tracking platform Yes. We can modify it but we need the base yes So either we can work parallel and discuss everyday what we are doing, We can share work and problems I totally agree we need to sync our progress frequently maybe this will be of some use: http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems The list is quite big. You have a look at them, I will too ok! and I found centos is now using mantis as bug tracker: http://www.mantisbt.org/demo.php , I will see the features mantis supports centos doesnt use bugzilla? note that mantis is not open source oh! that's bad we need to use open source tools no no it is open source http://www.mantisbt.org/download.php https://github.com/mantisbt/mantisbt yeah! about the reviewing platform how do we implement it Ours requirement is not exactly as bug tracking we need to interact with github at each point i agree with you what we build is a platform syncing data with github realtime I think once we decide on review platform we can divide work and start but we need review platform details first i think yes let's discuss in in detail; yeah what can it do commenting, tagging just like github's issue tracking tool i think yes Exactly it is like bugzilla + github yes! so what we do for this? can we base the platform on bugzilla bugzilla meets our requirements? i think no we need to develop new features what about other platforms? the list you gave we need to integrate with git, so the choice narrows down a bit so the first task is find a reviewing platform can we do this by today so that we can meet up tomorrow or day after tomorrow again discuss the API and changes in platform yes exactly and start working on it ok! Regarding dividing work One option is we work parallel as reviewing platform definitely requries that we both work together yes so we can work together. the only con is we become dependent. We won;t be able to quantify our individual effort. It will like a team. I am okay with it I think I am okay, too Great! So let's hunt a review platform fast. Once we finalise that we will work on timeline and then finally start coding :D ok! I've narrowed down the choice from the list to a few open source projects :D Great. Keep me informed about the same. I will too look at them :) with requirement of supporting git and being open source, there are three choices from the list: http://www.fusionforge.org , http://www.redmine.org , http://trac.edgewall.org and bugzilla okay I am trying redming http://demo.redmine.org I registered an account so we can try the demo, login: gsoc_test password: gsoc_test I will try it :) :D ---------------- Lei -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.george at RACKSPACE.COM Wed May 27 18:07:56 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 18:07:56 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal Message-ID: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Hello, I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html username: CarlGeorge proposed subject: Community Approved Third Party Repositories proposed location: http://wiki.centos.org/AdditionalResources/CATPR I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? Anyways, please create the article and grant me edit permission to it. Thanks! Carl George IUS CoreDev Team From ajb at elrepo.org Wed May 27 18:27:47 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 19:27:47 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> Message-ID: On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR From carl.george at RACKSPACE.COM Wed May 27 21:36:59 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Wed, 27 May 2015 21:36:59 +0000 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com>, Message-ID: <1432762564936.615@RACKSPACE.COM> Thanks Alan. While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? Carl George ________________________________________ From: centos-docs-bounces at centos.org on behalf of Alan Bartlett Sent: Wednesday, May 27, 2015 01:27 PM To: Mail list for wiki articles Subject: Re: [CentOS-docs] CATPR - new article for pending proposal On 27 May 2015 at 19:07, Carl George wrote: > Hello, > > I have been working on a proposal for CentOS that would allow certain third party repositories to have their release RPM included in the CentOS Extras repository, similar to how epel-release is included now. > > https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 > http://lists.centos.org/pipermail/centos-devel/2015-March/013097.html > > username: CarlGeorge > proposed subject: Community Approved Third Party Repositories > proposed location: http://wiki.centos.org/AdditionalResources/CATPR > > I'm not sure if this is the appropriate next step in the process (and no one seems to be able to tell me), but the page can always be deleted if the proposal dies. On that note, is there a standard/convention for articles that are proposals in progress (yet to be accepted)? Maybe prefixing the subject with [DRAFT] or [PROPOSAL]? > > Anyways, please create the article and grant me edit permission to it. Thanks! > > Carl George Hello Carl, I have created a CentOS wiki "home page" for you [1] and would suggest that you create your proposed page there under. [2] When it is ready, just announce its presence on this list and let a discussion commence. Alan. [1] http://wiki.centos.org/CarlGeorge [2] http://wiki.centos.org/CarlGeorge/CATPR _______________________________________________ CentOS-docs mailing list CentOS-docs at centos.org http://lists.centos.org/mailman/listinfo/centos-docs From ajb at elrepo.org Wed May 27 21:51:16 2015 From: ajb at elrepo.org (Alan Bartlett) Date: Wed, 27 May 2015 22:51:16 +0100 Subject: [CentOS-docs] CATPR - new article for pending proposal In-Reply-To: <1432762564936.615@RACKSPACE.COM> References: <8984b0fe2ac24aeeaa0535ba9a44e71a@544124-OEXCH02.ror-uc.rackspace.com> <1432762564936.615@RACKSPACE.COM> Message-ID: On 27 May 2015 at 22:36, Carl George wrote: > Thanks Alan. > > While working on this draft, I accidentally deleted the old content, and now I cannot edit the page anymore. Can you re-add my edit access on this page? > > Carl George Sure. No problem. Alan. From carl.george at RACKSPACE.COM Thu May 28 23:04:35 2015 From: carl.george at RACKSPACE.COM (Carl George) Date: Thu, 28 May 2015 23:04:35 +0000 Subject: [CentOS-docs] proposal for Community Approved Third Party Repos (CATPR) Message-ID: <86aaddfe0e6348c6901a94c5013b4103@544124-OEXCH02.ror-uc.rackspace.com> Howdy, I am proposing a process for 3rd party repositories that would allow them to have their release RPM added the the CentOS Extras repository. http://wiki.centos.org/CarlGeorge/CATPR I would like to start a discussion about approving the proposal and how to move forward. Carl George IUS CoreDev Team From kunaalus at gmail.com Fri May 29 19:33:52 2015 From: kunaalus at gmail.com (kunaal jain) Date: Sat, 30 May 2015 01:03:52 +0530 Subject: [CentOS-docs] Regarding GSoC project Message-ID: 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-development/ Lei made a great chart comparing the platforms. https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing 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 ?? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dougal at dougalmatthews.com Sat May 30 16:19:35 2015 From: dougal at dougalmatthews.com (Dougal Matthews) Date: Sat, 30 May 2015 17:19:35 +0100 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: On 29 May 2015 at 20:33, kunaal jain wrote: > > 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-development/ > > Lei made a great chart comparing the platforms. > > https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing > > 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. As a word of warning here, not all Markdown parsers and renderers are the same. GitHub's makes a number of additions and changes that go against the original (admittedly vague) spec. This could mean your previews are different and may not match the documentation build. An alternative approach would be to build the docs in CI and link to the built version in a comment on both systems. > > Please let us know, what you think about this? > > Regards, > Kunaal > > > -- > Regards, > Kunaal Jain > > > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > From yltt1234512 at gmail.com Sun May 31 04:26:52 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:26:52 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: <745C8184-DCB1-451B-82BB-71AC124E3412@gmail.com> >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From yltt1234512 at gmail.com Sun May 31 04:37:02 2015 From: yltt1234512 at gmail.com (Lei Yang) Date: Sun, 31 May 2015 12:37:02 +0800 Subject: [CentOS-docs] Regarding GSoC project In-Reply-To: References: Message-ID: >> >> 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-development/ >> >> Lei made a great chart comparing the platforms. >> >> https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=sharing >> >> 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. > > As a word of warning here, not all Markdown parsers and renderers are > the same. GitHub's makes a number of additions and changes that go > against the original (admittedly vague) spec. This could mean your > previews are different and may not match the documentation build. An > alternative approach would be to build the docs in CI and link to the > built version in a comment on both systems. > Thanks very much for your advice! We are planning to use Bugzilla, which doesn?t have a built-in code preview function. So we will need to use an external place to provide article review. Building the article in a CI and attach the link on github and reviewing platform would be a great solution. And about markdown standard, it will be a problem to solve. > >> >> Please let us know, what you think about this? >> >> Regards, >> Kunaal >> >> >> -- >> Regards, >> Kunaal Jain >> >> >> _______________________________________________ >> CentOS-docs mailing list >> CentOS-docs at centos.org >> http://lists.centos.org/mailman/listinfo/centos-docs >> > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs -------------- next part -------------- An HTML attachment was scrubbed... URL: