Search results for "contribute to wiki"

[Fedora-join] Old Fedora guy but new to fedora group - How to contribute?

by Manvendra Bhangui

I have been using Fedora for ages right from the first release. I am a C programmer since 1989. I know how to build RPM and Debian packages. I use the gnu autoconf, automake, libtool to build most of my work. I use vi and I use combination of RCS and git for version control. I am quite familiar with using many of the system calls. I strive to write portable code that compiles on linux and OSX. All my laptops, my mediacenter runs on Fedora and so I am familiar with Fedora for more than a decade. I want to contribute one of my major work - indimail-mta (a replacement for sendmail/postfix). indimail-mta has been built upon the original work by DJ Bernstein's qmail which was released to public domain in 2007 AFAIK. qmail as released by DJB is not FHS compliant. Also over the years, many have contributed to the source code in form of patches. I have fixed these issues (minor IMHO) and I do have RPMs released in public domain with the help of opensuse build service. Just recently I have been fixing things to make qmail FHS compliant and I thought I could also start working towards making a small contribution to fedora. But I am a newbie as far as the wonderful behind-the-scene-packaging that happens on Fedora. I have just created a fedora id and bugzilla id. Also I have been reading on how to contribute. I have so far read the following https://fedoraproject.org/wiki/Join_the_package_collection_maintainers and https://fedoraproject.org/wiki/Package_Review_Process I find the information overwhelming and I am not sure if I am reading the right documentation OR maybe it is my old dying grey cells. Any pointers on showing me the way would help me and I will try my best to meet the expectations and quality guidelines of the community. Also I am not sure if I can do this alone. So any help is welcome, especially from someone who loves qmail. Thank you in advance Regards Manvendra

7 years, 12 months

Re: [Fedora-join] Contributing to Fedora Project

by Ankur Sinha

On Wed, 2014-01-15 at 02:39 +0530, Santosh Kumar wrote: > Hello all, Hi Santosh, > My name is Santosh Kumar, final year Computer Science Engineer and a > FOSS enthusiast. I'm very much interested in contributing fedora > project. Welcome to the Fedora project! > I have worked upon flask and Django framework, so basically a python > programmer and have contributed to few of other open-source projects. > If there are beginner bugs which i can work upon to get started in > contributing to the community, it will be great!! I think Fedora infrastructure uses flask/django more than any other Fedora sub-group. You can see all our infrastructure related apps here: https://apps.fedoraproject.org/ Each of them has their own issue tracker. You can see them at the github project here: https://github.com/fedora-infra A list of "easyfix" bugs resides here: http://fedoraproject.org/easyfix/ There are actually quite a few, if you look at the list ;) We also run an askbot instance where there are a few bugs/RFEs that you could investigate. We file them with askbot upstream using the "askfedora" tag: http://askbot.org/en/questions/scope:all/sort:activity-desc/page:1/query:... With your experience in flask/django, I think the Fedora infrastructure team would fit well with your interests. If you're interested in some admin work, you could even help with puppet/ansible etc. that we use for deployment. Here's how to get started with Fedora infrastructure: http://fedoraproject.org/wiki/Infrastructure/GettingStarted Of course, this all python development work. There's a lot more going on in Fedora. Take a quick look at http://join.fedoraproject.org/ and if you have any queries about other tasks, fire away! :) -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG

10 years, 4 months

[Fedora-packaging] Updating one-off contributions documentation

by Otto Urpelainen

Hi, I would like to update the instructions for [One-off contributions][1] to packages. First, they are outdated, there is no need for external Git hosting since the anonymous checkout from src.fp.o method can now be used. Second, anyone needing that info is probably new to Fedora packaging and would appreciate something else than two terse paragraphs added to the bottom of very detailed article that they cannot actually utilize due to missing permissions. Currently, the documnetation is in the wiki. Am I correct that this kind of content should go to docs.fp.o? If so, I can make a pull request to move it. Either the whole _Joint he package collection maintainers_ page, or just the one-off contributions section. Does anybody here know what would be the correct course of action? Docs would be a better location for the one-off contributions section in particular. If anyone needs that information, they likely do not have the required groups in the Fedora Accounts to update the wiki. In case they discover anything is wrong or missing. With docs, that is not a problem, since the pull request method works there. Regards, Otto [1]: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#On...

3 years, 3 months

churchyard pushed to openshift-java-client (master). "Orphaned for 6+ weeks"

by notifications＠fedoraproject.org

Notification time stamped 2019-09-11 10:37:58 UTC From a4ad00091a8723f15e1fa2b0028d93758c086fd9 Mon Sep 17 00:00:00 2001 From: Miro Hrončok <miro(a)hroncok.cz> Date: Sep 11 2019 10:37:51 +0000 Subject: Orphaned for 6+ weeks --- diff --git a/.gitignore b/.gitignore deleted file mode 100644 index 5e8942f..0000000 --- a/.gitignore +++ /dev/null @@ -1,12 +0,0 @@ -.project -*/ -*.src.rpm -*.rpm -/openshift-java-client-2.0.3-7073708.tar.gz -/openshift-java-client-2.3.0-8de8554.tar.gz -/openshift-java-client-2.4.0-a97de13.tar.gz -/openshift-java-client-2.5.0-5579063.tar.gz -/openshift-java-client-2.6.0-03cb28d.tar.gz -/openshift-java-client-2.6.0-5acc248.tar.gz -/openshift-java-client-2.6.2-361de63.tar.gz -/openshift-java-client-2.7.0-9bb4e18.tar.gz diff --git a/dead.package b/dead.package new file mode 100644 index 0000000..5204a84 --- /dev/null +++ b/dead.package @@ -0,0 +1 @@ +Orphaned for 6+ weeks diff --git a/epl-v10.html b/epl-v10.html deleted file mode 100644 index 3998fce..0000000 --- a/epl-v10.html +++ /dev/null @@ -1,261 +0,0 @@ -<?xml version="1.0" encoding="ISO-8859-1" ?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml"> - -<head> -<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> -<title>Eclipse Public License - Version 1.0</title> -<style type="text/css"> - body { - size: 8.5in 11.0in; - margin: 0.25in 0.5in 0.25in 0.5in; - tab-interval: 0.5in; - } - p { - margin-left: auto; - margin-top: 0.5em; - margin-bottom: 0.5em; - } - p.list { - margin-left: 0.5in; - margin-top: 0.05em; - margin-bottom: 0.05em; - } - </style> - -</head> - -<body lang="EN-US"> - -<h2>Eclipse Public License - v 1.0</h2> - -THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE -PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR -DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS -AGREEMENT. - -1. DEFINITIONS - -"Contribution" means: - -a) in the case of the initial Contributor, the initial -code and documentation distributed under this Agreement, and -b) in the case of each subsequent Contributor: -i) changes to the Program, and -ii) additions to the Program; -where such changes and/or additions to the Program -originate from and are distributed by that particular Contributor. A -Contribution 'originates' from a Contributor if it was added to the -Program by such Contributor itself or anyone acting on such -Contributor's behalf. Contributions do not include additions to the -Program which: (i) are separate modules of software distributed in -conjunction with the Program under their own license agreement, and (ii) -are not derivative works of the Program. - -"Contributor" means any person or entity that distributes -the Program. - -"Licensed Patents" mean patent claims licensable by a -Contributor which are necessarily infringed by the use or sale of its -Contribution alone or when combined with the Program. - -"Program" means the Contributions distributed in accordance -with this Agreement. - -"Recipient" means anyone who receives the Program under -this Agreement, including all Contributors. - -2. GRANT OF RIGHTS - -a) Subject to the terms of this Agreement, each -Contributor hereby grants Recipient a non-exclusive, worldwide, -royalty-free copyright license to reproduce, prepare derivative works -of, publicly display, publicly perform, distribute and sublicense the -Contribution of such Contributor, if any, and such derivative works, in -source code and object code form. - -b) Subject to the terms of this Agreement, each -Contributor hereby grants Recipient a non-exclusive, worldwide, -royalty-free patent license under Licensed Patents to make, use, sell, -offer to sell, import and otherwise transfer the Contribution of such -Contributor, if any, in source code and object code form. This patent -license shall apply to the combination of the Contribution and the -Program if, at the time the Contribution is added by the Contributor, -such addition of the Contribution causes such combination to be covered -by the Licensed Patents. The patent license shall not apply to any other -combinations which include the Contribution. No hardware per se is -licensed hereunder. - -c) Recipient understands that although each Contributor -grants the licenses to its Contributions set forth herein, no assurances -are provided by any Contributor that the Program does not infringe the -patent or other intellectual property rights of any other entity. Each -Contributor disclaims any liability to Recipient for claims brought by -any other entity based on infringement of intellectual property rights -or otherwise. As a condition to exercising the rights and licenses -granted hereunder, each Recipient hereby assumes sole responsibility to -secure any other intellectual property rights needed, if any. For -example, if a third party patent license is required to allow Recipient -to distribute the Program, it is Recipient's responsibility to acquire -that license before distributing the Program. - -d) Each Contributor represents that to its knowledge it -has sufficient copyright rights in its Contribution, if any, to grant -the copyright license set forth in this Agreement. - -3. REQUIREMENTS - -A Contributor may choose to distribute the Program in object code -form under its own license agreement, provided that: - -a) it complies with the terms and conditions of this -Agreement; and - -b) its license agreement: - -i) effectively disclaims on behalf of all Contributors -all warranties and conditions, express and implied, including warranties -or conditions of title and non-infringement, and implied warranties or -conditions of merchantability and fitness for a particular purpose; - -ii) effectively excludes on behalf of all Contributors -all liability for damages, including direct, indirect, special, -incidental and consequential damages, such as lost profits; - -iii) states that any provisions which differ from this -Agreement are offered by that Contributor alone and not by any other -party; and - -iv) states that source code for the Program is available -from such Contributor, and informs licensees how to obtain it in a -reasonable manner on or through a medium customarily used for software -exchange. - -When the Program is made available in source code form: - -a) it must be made available under this Agreement; and - -b) a copy of this Agreement must be included with each -copy of the Program. - -Contributors may not remove or alter any copyright notices contained -within the Program. - -Each Contributor must identify itself as the originator of its -Contribution, if any, in a manner that reasonably allows subsequent -Recipients to identify the originator of the Contribution. - -4. COMMERCIAL DISTRIBUTION - -Commercial distributors of software may accept certain -responsibilities with respect to end users, business partners and the -like. While this license is intended to facilitate the commercial use of -the Program, the Contributor who includes the Program in a commercial -product offering should do so in a manner which does not create -potential liability for other Contributors. Therefore, if a Contributor -includes the Program in a commercial product offering, such Contributor -("Commercial Contributor") hereby agrees to defend and -indemnify every other Contributor ("Indemnified Contributor") -against any losses, damages and costs (collectively "Losses") -arising from claims, lawsuits and other legal actions brought by a third -party against the Indemnified Contributor to the extent caused by the -acts or omissions of such Commercial Contributor in connection with its -distribution of the Program in a commercial product offering. The -obligations in this section do not apply to any claims or Losses -relating to any actual or alleged intellectual property infringement. In -order to qualify, an Indemnified Contributor must: a) promptly notify -the Commercial Contributor in writing of such claim, and b) allow the -Commercial Contributor to control, and cooperate with the Commercial -Contributor in, the defense and any related settlement negotiations. The -Indemnified Contributor may participate in any such claim at its own -expense. - -For example, a Contributor might include the Program in a commercial -product offering, Product X. That Contributor is then a Commercial -Contributor. If that Commercial Contributor then makes performance -claims, or offers warranties related to Product X, those performance -claims and warranties are such Commercial Contributor's responsibility -alone. Under this section, the Commercial Contributor would have to -defend claims against the other Contributors related to those -performance claims and warranties, and if a court requires any other -Contributor to pay any damages as a result, the Commercial Contributor -must pay those damages. - -5. NO WARRANTY - -EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS -PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS -OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, -ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY -OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely -responsible for determining the appropriateness of using and -distributing the Program and assumes all risks associated with its -exercise of rights under this Agreement , including but not limited to -the risks and costs of program errors, compliance with applicable laws, -damage to or loss of data, programs or equipment, and unavailability or -interruption of operations. - -6. DISCLAIMER OF LIABILITY - -EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT -NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, -INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING -WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF -LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING -NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR -DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED -HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - -7. GENERAL - -If any provision of this Agreement is invalid or unenforceable under -applicable law, it shall not affect the validity or enforceability of -the remainder of the terms of this Agreement, and without further action -by the parties hereto, such provision shall be reformed to the minimum -extent necessary to make such provision valid and enforceable. - -If Recipient institutes patent litigation against any entity -(including a cross-claim or counterclaim in a lawsuit) alleging that the -Program itself (excluding combinations of the Program with other -software or hardware) infringes such Recipient's patent(s), then such -Recipient's rights granted under Section 2(b) shall terminate as of the -date such litigation is filed. - -All Recipient's rights under this Agreement shall terminate if it -fails to comply with any of the material terms or conditions of this -Agreement and does not cure such failure in a reasonable period of time -after becoming aware of such noncompliance. If all Recipient's rights -under this Agreement terminate, Recipient agrees to cease use and -distribution of the Program as soon as reasonably practicable. However, -Recipient's obligations under this Agreement and any licenses granted by -Recipient relating to the Program shall continue and survive. - -Everyone is permitted to copy and distribute copies of this -Agreement, but in order to avoid inconsistency the Agreement is -copyrighted and may only be modified in the following manner. The -Agreement Steward reserves the right to publish new versions (including -revisions) of this Agreement from time to time. No one other than the -Agreement Steward has the right to modify this Agreement. The Eclipse -Foundation is the initial Agreement Steward. The Eclipse Foundation may -assign the responsibility to serve as the Agreement Steward to a -suitable separate entity. Each new version of the Agreement will be -given a distinguishing version number. The Program (including -Contributions) may always be distributed subject to the version of the -Agreement under which it was received. In addition, after a new version -of the Agreement is published, Contributor may elect to distribute the -Program (including its Contributions) under the new version. Except as -expressly stated in Sections 2(a) and 2(b) above, Recipient receives no -rights or licenses to the intellectual property of any Contributor under -this Agreement, whether expressly, by implication, estoppel or -otherwise. All rights in the Program not expressly granted under this -Agreement are reserved. - -This Agreement is governed by the laws of the State of New York and -the intellectual property laws of the United States of America. No party -to this Agreement will bring a legal action under this Agreement more -than one year after the cause of action arose. Each party waives its -rights to a jury trial in any resulting litigation. - -</body> - -</html> \ No newline at end of file diff --git a/openshift-java-client.spec b/openshift-java-client.spec deleted file mode 100644 index c8ce684..0000000 --- a/openshift-java-client.spec +++ /dev/null @@ -1,126 +0,0 @@ -%global commit 9bb4e186dd287f95bfd04e886687b992d9c7306d -%global shortcommit %(c=%{commit}; echo ${c:0:7}) - -Name: openshift-java-client -Version: 2.7.0 -Release: 10%{?dist} -Summary: OpenShift Java Client - -License: EPL -URL: http://openshift.redhat.com -Source0: https://github.com/openshift/%{name}/archive/%{commit}/%{name}-%{version}... -BuildArch: noarch - -BuildRequires: maven-local -BuildRequires: mvn(com.jcraft:jsch) -BuildRequires: mvn(commons-io:commons-io) -BuildRequires: mvn(junit:junit) -BuildRequires: mvn(log4j:log4j) -BuildRequires: mvn(org.apache.commons:commons-compress) -BuildRequires: mvn(org.codehaus.mojo:properties-maven-plugin) -BuildRequires: mvn(org.jboss:jboss-dmr) -BuildRequires: mvn(org.jboss:jboss-parent:pom:) -BuildRequires: mvn(org.mockito:mockito-core) -BuildRequires: mvn(org.slf4j:slf4j-api) -BuildRequires: mvn(org.slf4j:slf4j-log4j12) - -%description -This is a client for OpenShift written in java. It pretty much offers all -features that are currently available in the rhc-* command line tools -(create/rename a domain, create/destroy applications, list all existing -applications, available cartridges, embed cartridges etc.). - -%package javadoc -Summary: Javadoc for %{name} - -%description javadoc -API documentation for %{name}. - -%prep -%setup -qn %{name}-%{commit} - -%pom_remove_dep org.easytesting:fest-assert - -%build -# Tests skipped because of wrong junit version -# (Fedora is 4.10, this expects 4.8) -%mvn_build --skip-tests - -%install -%mvn_install - -%files -f .mfiles -%dir %{_javadir}/%{name} -%license license epl-v10.html - -%files javadoc -f .mfiles-javadoc -%license license epl-v10.html - -%changelog -* Thu Jul 25 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.7.0-10 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild - -* Fri Feb 01 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.7.0-9 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild - -* Fri Jul 13 2018 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.7.0-8 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild - -* Thu Feb 08 2018 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.7.0-7 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild - -* Thu Jul 27 2017 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.7.0-6 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild - -* Sat Feb 11 2017 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.7.0-5 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild - -* Sat Oct 15 2016 gil cattaneo <puntogil(a)libero.it> 2.7.0-4 -- add missing build requires: jboss-parent -- introduce license macro -- minor changes to adapt to current guideline - -* Thu Feb 04 2016 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.7.0-3 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild - -* Thu Jun 18 2015 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org> - 2.7.0-2 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild - -* Fri May 08 2015 Gerard Ryan <galileo(a)fedoraproject.org> - 2.7.0-1 -- Update to 2.7.0.Final - -* Mon Nov 10 2014 Gerard Ryan <galileo(a)fedoraproject.org> - 2.6.2-1 -- Update to 2.6.2.Final - -* Sat Sep 13 2014 Gerard Ryan <galileo(a)fedoraproject.org> - 2.6.0-1 -- Update to 2.6.0.Final - -* Thu Jul 17 2014 Gerard Ryan <galileo(a)fedoraproject.org> - 2.6.0-0.1 -- Update to 2.6.0-SNAPSHOT - -* Sat Jun 07 2014 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org> - 2.5.0-2 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild - -* Sat Nov 30 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.5.0-1 -- Update to version 2.5.0.Final - -* Sun Oct 13 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.4.0-1 -- Update to version 2.4.0.Final - -* Sat Jul 27 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.3.0-2 -- Add BR maven-resources-plugin to fix rawhide - -* Wed Jul 24 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.3.0-1 -- Update to latest upstream version 2.3.0 - -* Fri Mar 29 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.0.3-3 -- Fix changelog. -- Remove unneeded Requires. -- Added epl-v10.html as a doc to main and javadoc packages. - -* Wed Mar 20 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.0.3-2 -- Update to fix licensing and new Base64Coder implementation. -- Use new maven macros. - -* Sun Jan 20 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.0.3-1 -- Initial package. diff --git a/sources b/sources deleted file mode 100644 index e1d3e0b..0000000 --- a/sources +++ /dev/null @@ -1 +0,0 @@ -865a1d686368c70395a6f868dcedee23 openshift-java-client-2.7.0-9bb4e18.tar.gz https://src.fedoraproject.org/rpms/openshift-java-client/c/a4ad00091a8723...

4 years, 8 months

Re: Proposal for new docs workflow

by Paul W. Frields

On Fri, Oct 09, 2015 at 03:32:15PM -0500, Adam Miller wrote: > Hello all, > We currently have a lot of documentation in the Fedora Wiki[0][1] > that is either old and out of date or just not relevant anymore and I > know many people don't like to work in the wiki so I would like to > make a proposal to change the documentation workflow so that we can > improve the docs for ourselves and for potentially new community > contributors who would like to join the fun. > > I would first like to explain a couple options I have about Release > Engineering documentation first. > > I believe we should ultimately have two "types" of documentation for > different roles that contributors would like to take on. > > I think we can define this as "Rel-Eng Ops" and "Rel-Eng Tools Devs" such that: > > Rel-Eng Ops are those who are doing the work to create composes, > manage the infrastructure, the day to day operations, and the like. > This is where the Standard Operating Procedures[1] for Fedora Release > Engineering should live as well as an on-boarding guide for new > community members who would like to know more about Fedora Rel-Eng > and/or join the group and share in the work. > > Rel-Eng Tools Devs are people who are going to be collaborating on > release tools upstream such as pungi, mash, mock, koji, and others. > These tools should each independently have their own documentation and > test suites in order to describe how community developers who would > like to contribute to these tools can do so. Things here that should > be documented are common development workflows, tools that are used to > make development/contribution easier, coding guidelines, contribution > and pull request workflow guidelines, etc. > > I think the tools themselves should be referenced in the SOPs or > "Rel-Eng Ops" documentation in order to bridge those who are using the > tools to the tools themselves as someone participating in one form of > contribution (working on Ops tasks) may very well also participate in > the other (contributing code to tools) or vice versa. I definitely > don't want there to be any impression that these should be disjoint > types of contribution/contributors but more so that they can stand on > their own independently if someone out in the community who would like > to contribute is more interested in one area versus the other. > > Proposal: > > I would like to start with the RelEng Ops documentation as it's the > most "single point of entry", has a lot of docs that can be > "translated" from the Wiki along with getting updates, and would be a > good resource to have updated and documented in terms of the > on-boarding of potential new contributors which could lead to interest > in other tools that need individual documentation. > > We would format all documentation using ReStructuredText[2] and > sphinx-doc[3] as that is the defacto standard in the python community > (which most of our tooling is written in), it's easy to use, and is > already in use by the Fedora Apps, Infrastructure, and QA teams. > (There are more example but I thought these were enough) > > I propose these docs live in the releng pagure repository > (https://pagure.io/releng) and possibly have a space on > readthedocs.org[4] as it's already under heavy use with Fedora > projects with docs written in rst/sphinx.[5][6][7][8][9] > > We could alternatively use pagure itself for docs hosting as pagure > hosts it's own docs also written in sphinx[10][11][12], it's not as > automatic for rendering and would take a little bit of scripting but > it's certainly an option. > > If you've made it this far you get a cookie or something, but thank > you for sticking with it. > > I'm open to questions, comments, general feedback, and of course > snide remarks. Minor technical point, but do or Pierre think it's possible to integrate readthedocs functionality with Pagure, such that a push to your Sphinx docs would regenerate the site there? Obviously readthedocs is itself FOSS so perhaps we could contribute a patch for this upstream, since it seems like it's at least partly a function of that site. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com

8 years, 7 months

Re: need help in contributing to se-linux policy development

by Dominick Grift

On Sun, Jan 03, 2010 at 09:22:07PM +0530, sai ganesh wrote: > hi, > my name is sai. i am a > fedora-ambassador<https://fedoraproject.org/wiki/user:ganesai>.i > want to contribute to the development of se-linux policies.i am a Redhat > certified se-linux policy administrator.i want to contribute to the > development of se-linux policies.how can i contribute ? > whom should i contact? You can suggest policy here on this list. You can join #selinux and #fedora-selinux on irc://irc.freenode.org. You can contribute directly upstream here: http://oss.tresys.com/projects/refpolicy/wiki/HowToContribute. You can suggest policy in bugzilla.redhat.com in the selinux-policy component. Daniel "dwalsh" Walsh (RedHat) is Fedora/Redhat SELinux policy maintainer and Chris "Pebenito" Pebenito (Tresys) is Reference policy maintainer (upstream to Fedora). > > i have already tried contacting the owners of the se-linux packages.i > didn't get any response. > > > > -- > s.saiganesh > “The Linux philosophy is 'Laugh in the face of danger'. Oops. Wrong One. 'Do > it yourself'. Yes, that's it > -- > fedora-selinux-list mailing list > fedora-selinux-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/fedora-selinux-list

14 years, 5 months

[Ambassadors] About Fedora Contribution and probation

by gnu boi

Hi Everybody, I am Ujjwol Lamichhane <https://fedoraproject.org/wiki/Ujjwol>. In the fedora wiki it is written that, *------------ For the first 30 days, the status of a newbie Ambassador will be "on probation", during which time they have a chance to prove themselves to the group by contributing to the project. ------------------- *What does contributing here means? And in Fedora 10 Release Party in Kathmandu, i am giving presentation on fedora 10's features, and giving fedora 10 release news to local news media, blogging on fedora 10 on my blog, also writing article in local magazine of nepal open-source community, FOSS Nepal. Will this task makes me permanent ambassador not "on probation". I have really contributed to fedora since long time. Showing fedora in Software Freedom and also promoted it in my college. And if is there any thing i can do to contribute to fedora, please let me know. and also tell about probation also.. Thanks Everybody

15 years, 6 months

[Fedora-join]Re: Contribution

by Justin W. Flory

Hello Shraddha, and welcome to Fedora! The Fedora Kernel Team has several resources in place to help new contributors get started with contributing. The wiki page for the Kernel team has a lot of info that you should find helpful. https://fedoraproject.org/wiki/Kernel To get started, I would first advise you to create an account in the Fedora Account System if you have not done so already. You can find info on this here: https://fedoraproject.org/wiki/Account_System Once you are in FAS, I would recommend subscribing to the Fedora Kernel mailing list. I would send a similar introduction as you sent here to our mailing list. https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.... Finally, the last thing you can do to get jumpstarted in helping with the Fedora kernel is by using IRC for instant messaging with the Kernel team. If you are unfamiliar with IRC, you can learn more about it here: http://fedoraproject.org/wiki/IRC The kernel team usually resides in #fedora-kernel on the Freenode IRC network. I would recommend using an IRC client (like HexChat) or the Freenode webchat (webchat.freenode.net) to connect to IRC and talk with the team. Hopefully this will help answer some of your questions about getting started. If you have any problems with getting started with the Kernel team, feel free to email us back and we will do our best to support you in getting started! If you have specific questions about contributing to the Kernel, I would contact the folks over on that mailing list and IRC channel. Although I will use fair warning, it is a national holiday in the United States (Thanksgiving), so you may be slow to get responses from some contributors until the next Monday. There should be some other international contributors who can help get you started though! Again, welcome to the Fedora Project, and we're glad to have you here with us. :) -- Cheers, Justin W. Flory jflory7(a)gmail.com On 11/26/2015 11:34 AM, Shraddha Barke wrote: > Hello guys! > > I'm Shraddha , an opensource enthusiast and a regular contributor to > the linux-kernel project. I'm currently an intern at Linux Kernel > selected through the Outreachy program. I started contributing to > opensource only 5 months ago but I'm already quite active. I would like > to join the fedora project and work on kernel development or web > technologies. Any help on getting started is appreciated :) > > Kind Regards, > > Shraddha > > -- > Shraddha > > > _______________________________________________ > fedora-join mailing list > fedora-join(a)lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/fedora-join@lists.fedoraprojec... >

8 years, 6 months

Re: Self-Introduction: hello everyone

by Petr Bokoc

Hi Vincent! I'm glad you want to contribute, however, unfortunately the docs project doesn't maintain the Wiki (I know, it's a bit counterintuitive). We take care of content on the docs portal (https://docs.fedoraproject.org/). The Wiki, content-wise, doesn't actually "belong" to any one group - people get edit rights automatically when they join any group as contributors, be it docs, marketing, a technical SIG... If you're only interested in contributing to the Wiki, then please see https://fedoraproject.org/wiki/Help:Editing#Gaining_Edit_Access - especially point 3. Basically you should open a ticket for infra to get access if you don't want to get involved in any other aspect of Fedora right now. If you change your mind and decide you want to contribute to the docs published on docs.fp.o, let me know. (Note that not all of these docs are maintained by us either; the Docs Project actively maintains the portal and some of the docs listed under User Docs, the rest is split among various groups maintaining their own docs repos and we make sure they're published and provide help if needed.) Cheers, Petr On 10/17/19 10:47 PM, Vincent Rubiolo [IoT.bzh] wrote: > Hi everyone, > > I've created a new FAS account last week as I am interested in fixing > up/contributing things on the Fedora wiki. Once my account has been > created, I was told I need sponsorship to get out of the 'CLA+1' > category so here I am (thanks to Pierre-Yves Chibon for the > confirmation on the process!). > > I have been using Linux for quite some time now (2001): I started with > Debian and then Gentoo Linux, then Mandrake and Ubuntu. I have been > using Fedora for ~5 years now and I love it (a great mix of current > and sleek software along with stability). > > I have been wanting to contribute back in one form or the other for > some time, usually I report bugs or fix documentation as a start > (hence the introduction on this list :). I love free/libre software > and think it is very important in the SW/freedom ecosystem. > > Skillset-wise, I work as an embedded computing engineer. I have worked > on RTOSes as well as certification projects (DO-178C like). I know > C/assembly and OSes but also Python as well as cloud-related > technologies (having worked on Kubernetes/Docker/Helm and AWS/GCP). I > am currently doing infrastructure/container work (another great reason > I like Fedora!) around Automotive Grade Linux projects. I am also fond > of maker-related technologies like 3D printing. > > I am now back on the CEST zone, after living for several years in the > US (PDT/San Francisco). As I said, so far, I am interested in fixing > pages I use on the wiki for typos/inacurracies/etc. > > Thanks for reading and have a great day everyone! > > Best, > > Vincent > > PS: I have noted the bits about my GPG key and I am working on it. > Will post a followup when this is done. > _______________________________________________ > docs mailing list -- docs(a)lists.fedoraproject.org > To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org

4 years, 7 months

[Bug 812758] Review Request: trader - Star Traders, a simple game of interstellar trading

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=812758 William Moreno <williamjmorenor(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |182235 (FE-Legal) --- Comment #22 from William Moreno <williamjmorenor(a)gmail.com> --- I think you can create a .desktop file with terminal=True https://fedoraproject.org/wiki/Packaging:Guidelines#Desktop_files You SHOULD provide a .xml.appdata file if you not provide the appdata information users will can not find this game in Gnome Software. https://fedoraproject.org/wiki/Packaging:AppData You must use the %license tag for the COPYING file. Did you read the FPCA, by default all spec files in Fedora are released under the MIT License "Current Default License", with respect to a Contribution, means (i) if the Contribution is Code, the MIT License, and (ii) if the Contribution is Content, CC-BY-SA supplemented by Moral Rights Clause Waiver and GPL Relicensing Permission." Any way: 2. Licensed Contributions. If Your Contribution is Licensed, Your Contribution will be governed by the terms under which it has been licensed. So just include the spec file in the project source and by this way your code and the spec file will be covered by the same license, any way there is not need to put a license adivisory in the spec so all the spec files are under a very permisive license. Any way we can ask to legal. So I will request to Legal to please consider if we can continue with this review with the legal notice in the spec about GPLv3. Any way you can do some informal reviews by the way. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=182235 [Bug 182235] Fedora Legal Tracker -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component

8 years, 4 months

Search results for query "contribute to wiki"