similar to: GSoC - Syncing docs between GitHub and CentOS's git repo

Hi Kunal! Thanks for your reply! I think the official mirroring is a great method because of higher efficiency. Another thing I am trying to solve is how to retrieve and store all the discussion / issue / PR on GitHub? These functions are great for a doc toolchain. However we shouldn?t rely on GitHub as a part of our project. My plan now is to use bugs.cents.org as a place to discuss about docs

On Apr 7, 2015 9:28 AM, "? ?" <yltt1234512 at gmail.com> wrote: > > Hi Kunal! > > Thanks for your reply! I think the official mirroring is a great method because of higher efficiency. > > Another thing I am trying to solve is how to retrieve and store all the discussion / issue / PR on GitHub? These functions are great for a doc toolchain. However we shouldn?t

Hi! I am applying for Google Summer of Code 2015 with a project creating a new doc toolchain for CentOS. I plan to use GitHub to store a copy of the documentation, and users can send fork / send PR to this repo. Then a server program monitors this repo and syncs changes between GitHub and CentOS?s own git repo. So the key is to automatically sync repo between GitHub and CentOS. I think there

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 :

Hi Lei, > On Jun 20, 2015, at 11:21 AM, Lei Yang <yltt1234512 at gmail.com> wrote: I am sorry it has taken me so long to test this workflow. > Hi, > > Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute.

Hi, Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute. This is the workflow of the prototype: 1. Contributor creates a new pull request on GitHub 2. A corresponding issue is automatically created on Pagure 3. Staff and

-----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

Hi, I have submitted my proposal for the above said idea. I have researched about this from past two weeks, put the proposed workflow in the proposal. I am in contact with Karsten from last two weeks. However I have not added exact implementation details about tools, which will be better if mentor discusses first. Please suggest changes. Regards, Kunal Jain

Hi guys, I have submitted my proposal on google-melange. I have been active in discussion regarding this on centos-docs as well with Karsten. I have created a small demo tool chain, to have a clarity on how process will flow and how site can be generated on git commits and deploying to hosting platform. You can find the code as well as the live version at :

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

On Thu, Jul 9, 2015 at 1:19 AM, Brian (bex) Exelbierd <bex at pobox.com> wrote: > Hi Lei, > > Hi, I am Kunaal the other GSoC student working on this toolchain. > On Jun 20, 2015, at 11:21 AM, Lei Yang <yltt1234512 at gmail.com> wrote: > > > I am sorry it has taken me so long to test this workflow. > Thanks a lot! We need testers and input from community.

Hi Kartsen, you'll have my proposal by the end of the day. I am not good at writing content. :( I have sorted out all the technicalities though. Regards, Kunal Jain On Tue, Mar 24, 2015 at 5:48 AM, Karsten Wade <kwade at redhat.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Kunaal: > > I know you are still researching, but I think you may have

> ? 2015?6?5????6:10?Karsten Wade <kwade at redhat.com> ??? > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 06/04/2015 12:58 PM, Pete Travis wrote: > >> >> I'm tentatively planning on working pagure[0] into the Fedora Docs >> toolchain. It handles issue tracking, process >> documentation/contribution guidelines, and of course

Dear Aki, i think I got it. Many thanks. it has to do with the permission settings. On Mon, Feb 25, 2019 at 12:59 PM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > drwx-----x kunal kunal Storage > > I'm guessing this point is being more restrictive. Can you try changing > this into 0755? > > Also suddenly you are no longer using vmail but random user IDs. This

drwx-----x kunal kunal Storage I'm guessing this point is being more restrictive. Can you try changing this into 0755? Also suddenly you are no longer using vmail but random user IDs. This only works with vmail. Aki > On 25 February 2019 19:56 Kunal A. <kunal.oa at gmail.com> wrote: > > > Hi, > Yes. Output ;- > > dr-xr-xr-x root root / > drwxr-xr-x root

On Tue 2019-03-26 @ 10:40:49 AM, Ilia Mirkin wrote: > Just looked over the projects... they all seem valid Thank you for taking the time to have a look and provide feedback! > but are there > people who could realistically mentor a GSoC student for these? IMHO > unless mentors can be identified, these should all be archived. Attracting mentors is probably the hardest part of running

Hey Aki, Sorry for the trouble but I am still unable to get it working. The file permissions for upper files are now drwxr-xr-x. but I think they need to be drwxr-x--x+ ? Any idea how to change it to that? Error log is below:- doveadm(lightdm): Error: Can't open mailbox Storage/Email: stat(/run/media/computer/Storage/Email/tmp) failed: Permission denied (euid=976(lightdm) egid=976(lightdm)

On Thu, Jul 09, 2015 at 02:11:26AM +0530, kunaal jain wrote: > On Thu, Jul 9, 2015 at 1:19 AM, Brian (bex) Exelbierd <bex at pobox.com> > They have both a private git (with gerrit) and a github repo.A If you > open a PR on github it is closed by a bot with instructions to submit > the PR via gerrit to their private repo.A When the PR is resolved and >

On 08/20/2015 02:57 AM, Karsten Wade wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 08/03/2015 12:52 PM, Fabian Arrotin wrote: >> On 03/08/15 18:23, kunaal jain wrote: >> Is that possible to have an overview of the infra and goals (aka >> the architecture) of this GSoC doc project ? that would help >> understanding, as I agree that I'm

On Tue, Jul 28, 2015 at 8:47 AM, kunaal jain <kunaalus at gmail.com> wrote: > Lei and I have been working on the project, based on community input. We > have implemented two way sync between github and pagure as suggest by many. > > Now we want build the site and display it to user. There are number of > options mkdocs, hugo(docker uses it now) etc. > > There are pros