search for: pagure

...roject (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 contributor discuss on Pagure 4. When the pull request can be accepted, it is marked as ?fixed?, and the pull request on github is automatically merged 5. New change is synced to Pagure (doc website will update according to Pagure repo, to be implemented later) We have made a prototyp...

...t; 1. Contributor creates a new pull request on GitHub > > > A fairly well understand platform with lots of potential users - cool. > Github also has some social cachet. > That's the aim. Exploit this social cachet. > > 2. A corresponding issue is automatically created on Pagure > 3. Staff and contributor discuss on Pagure > > > This part is a bit odd to me, today. I believe your goal is to make sure > the discussion happens in a CentOS controlled space in case github ever > becomes an issue. However, it seems odd that we don't just mirror the >...

...it easy for people to contribute new, short-form content articles to the Project with an ability to push them outward to relevant upstream projects. ==Workflow== 1. The user authors content in markdown format and creates a pull request on Github. 2. The backend service mirrors the pull request to pagure and creates a issue. 3. The doc is built and a link is provided to preview the doc. 5. Staff reviews the docs, gives comments either on pagure or github (two way synced) 4. Once the staff approves the doc is built and doc site updated. ==Infra== 1. A backend server listing to Github and Pagure we...

...te repo.A When the PR is resolved and > merged in the private repo, the entire commit is pushed to github > awarding the social "status" that comes from a commit. I am not > suggesting we use gerrit. > > I agree. Main reason is because of two way sync of pagure and github. Once > that done, user even doesn't need to be aware that pagure exists. I agree > right now we are doing something like openstack which you described, but > we dont want that.A > [...] > > We use Pagure as a part of the toolchain. Pagure is an e...

...I understand the goals here: > This is the workflow of the prototype: > 1. Contributor creates a new pull request on GitHub A fairly well understand platform with lots of potential users - cool. Github also has some social cachet. > 2. A corresponding issue is automatically created on Pagure > 3. Staff and contributor discuss on Pagure This part is a bit odd to me, today. I believe your goal is to make sure the discussion happens in a CentOS controlled space in case github ever becomes an issue. However, it seems odd that we don't just mirror the whole PR over (see below for...

...oper documentation. An entire Bugzilla instance > is another thing, however -- web server, PHP code, database, and so fort > h. > > Are you sure that bugs.centos.org cannot work well enough? > > Regards, > > - - Karsten > - -- > I'm tentatively planning on working pagure[0] into the Fedora Docs toolchain. It handles issue tracking, process documentation/contribution guidelines, and of course repo management and pull requests. It might fit for CentOS docs as well. [0] https://pagure.io/pagure --Pete -------------- next part -------------- An HTML attachment was s...

> ? 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 repo >> management and pull requests. It might fit for CentOS docs as >> well. >> >> [0] https://pagure.io/pagure > > Oh now...

...short-form content articles to the > Project with an ability to push them outward to relevant upstream > projects. > > ==Workflow== > > 1. The user authors content in markdown format and creates a pull > request on Github. > 2. The backend service mirrors the pull request to pagure and creates a issue. > 3. The doc is built and a link is provided to preview the doc. > 5. Staff reviews the docs, gives comments either on pagure or github > (two way synced) > 4. Once the staff approves the doc is built and doc site updated. > > ==Infra== > > 1. A backend...

...uld start with the note that the basic project is complete. I > would be releasing the prototype on a separate thread. But for the > discussion sake the workflow will look like this : Authors > contribute content in markdown format, on github. The pull request > created gets mirrored to pagure thus saving dependency on github. > Also the PR content is built using CI to preview how it looks. The > PR is two way synced between the platforms, so that individual can > use pagure or github. Once staff approves the post, website is > built and deployed. > <snip> So, tr...

Due to a scheduled pagure upgrade, we'll have to move the existing Pagure instance (aka https://git.centos.org) to a new node. Migration is scheduled for """"Monday June 13rd, 7:00 am UTC time"""". You can convert to local time with $(date -d '2022-06-13 07:00 UTC') The...

...AN database, for an > > arbitrary list of RPMs. That would be perfect. In theory, this should > > be possible with dnf, but when I tried, I failed (or my script would > > theoretically work, but it would take ages to complete). I also took a > > look at releng's repos on Pagure, but I didn't find any tool to do > > this either. > > > > We should bring this to devel, maybe ask Miro and other Python folks > > who may have The Method(TM), as they are rebuilding stuff on a daily > > basis. > > I think that I meant the way that the pytho...

-----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 repo > management and pull requests. It might fit for CentOS docs as > well. > > [0] https://pagure.io/pagure Oh now that is quite interesting news....

...note that the basic project is complete. I >> would be releasing the prototype on a separate thread. But for >> the discussion sake the workflow will look like this : Authors >> contribute content in markdown format, on github. The pull >> request created gets mirrored to pagure thus saving dependency on >> github. Also the PR content is built using CI to preview how it >> looks. The PR is two way synced between the platforms, so that >> individual can use pagure or github. Once staff approves the >> post, website is built and deployed. > > &...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There have been some questions about how the GSoC project interacts with the existing documentation work that happens around the wiki. Let's get all the open questions in to this thread and discuss them. Lei, Kunaal -- What other open questions do we have? Anyone else with open questions? The GSoC project is supposed to be additive to what we

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

...> --- > Lee No, it's not part of RHEL9 , and it's built and maintained by the Kmods SIG (see https://sigs.centos.org/kmods/) as a community project. They were building it first for Stream 9 and later asked to also build for/against RHEL9 kernel when it was available (see https://pagure.io/centos-infra/issue/786) Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc:...

...;s probably more of a cfe-dev topic), As a follow-up to that old thread about -D_FORTIFY_SOURCE=n http://lists.llvm.org/pipermail/cfe-dev/2015-November/045845.html And, more recently, to this fedora thread where clang/llvm -D_FORTIFY_SOURCE support is claimed to be only partial: https://pagure.io/fesco/issue/2020 I dig into the glibc headers in order to have a better understanding of what's going on, and wrote my notes here: https://sergesanspaille.fedorapeople.org/fortify_source_requirements.rst TL;DR: clang does provide a similar compile-time checking as gcc, but no runtime...

...s another thing, however -- web server, PHP code, database, and so fort > > h. > > > > Are you sure that bugs.centos.org cannot work well enough? > > > > Regards, > > > > - - Karsten > > - -- > > > > I'm tentatively planning on working pagure[0] into the Fedora Docs > toolchain. It handles issue tracking, process documentation/contribution > guidelines, and of course repo management and pull requests. It might fit > for CentOS docs as well. > Can you tell us about Fedora Docs toolchain? We can surely help each other if our...

On 11/12/17 10:22, Thibaut Perrin wrote: > Hello Fabien, > > First, thank you for even trying for what seems to be an impossible task :( > > Quick points :? > - if it was decided not to continue, what would happen to the current > wiki ? Dismantled or would it remain as read-only for documentation > purpose ? > - What about Sphinx

Hi, 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 and cons to each site generator. To use hugo, we need the user to have hugo installed too, and than he needs to run hugo command to create a new...