Search results for "contribute to wiki"

[Fedora-join] Beat writers required for the FWN

by Ankur Sinha

Hi folks, FWN is a great way of contributing to Fedora. You basically read up on various mailing lists and summarize what's been going on. It keeps you (and the community) up to date on happenings within the community (and is also a great way to practice your writing skills!) Please read the mail below for more information: -------- Forwarded Message -------- > From: Rashadul Islam <rashadul(a)fedoraproject.org> > Reply-to: ambassadors(a)lists.fedoraproject.org > To: Fedora Weekly News team discussion <news(a)lists.fedoraproject.org>, > Fedora Marketing team <marketing(a)lists.fedoraproject.org>, > ambassadors(a)lists.fedoraproject.org > Subject: [Ambassadors] Fedora Weekly News(FWN) Issue 297 > Date: Tue, 12 Mar 2013 11:31:30 -0400 > > > > There has been a long break to publish the Fedora Weekly News(FWN). > Fedora experts, ambassadors, and contributors are playing an > enthusiastic role for the development of Fedora marketing, > development, design, infrastructure, documentation, and other. All of > us are very strongly tied by our dedication for Fedora. > > > > Now, it is the responsibility of the FWN News team to explore all the > Fedora mainstream contribution to all contributors and news editor all > over the world. It is the honor of Fedora Weekly News team. > > > > Please step forward to contribute at the FWN team and spread the news > to all. Your contribution can make a big difference for the community. > > > > Brief: > > Releasing FWN Issue 297 on March 13, 2013 > > New bee is welcome to join in the team > > > > For more information, please visit https://fedoraproject.org/wiki/FWN > > > > -Rashadul Islam > > 0x5557BFAC -- Thanks, Warm regards, Ankur: "FranciscoD" Please only print if necessary. Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG http://fedoraproject.org/wiki/User:Ankursinha http://dodoincfedora.wordpress.com/

11 years, 2 months

[fedora-india] Beat writers required for the FWN

by Ankur Sinha

Hi folks, FWN is a great way of contributing to Fedora. You basically read up on various mailing lists and summarize what's been going on. It keeps you (and the community) up to date on happenings within the community (and is also a great way to practice your writing skills!) Please read the mail below for more information: -------- Forwarded Message -------- > From: Rashadul Islam <rashadul(a)fedoraproject.org> > Reply-to: ambassadors(a)lists.fedoraproject.org > To: Fedora Weekly News team discussion <news(a)lists.fedoraproject.org>, > Fedora Marketing team <marketing(a)lists.fedoraproject.org>, > ambassadors(a)lists.fedoraproject.org > Subject: [Ambassadors] Fedora Weekly News(FWN) Issue 297 > Date: Tue, 12 Mar 2013 11:31:30 -0400 > > > > There has been a long break to publish the Fedora Weekly News(FWN). > Fedora experts, ambassadors, and contributors are playing an > enthusiastic role for the development of Fedora marketing, > development, design, infrastructure, documentation, and other. All of > us are very strongly tied by our dedication for Fedora. > > > > Now, it is the responsibility of the FWN News team to explore all the > Fedora mainstream contribution to all contributors and news editor all > over the world. It is the honor of Fedora Weekly News team. > > > > Please step forward to contribute at the FWN team and spread the news > to all. Your contribution can make a big difference for the community. > > > > Brief: > > Releasing FWN Issue 297 on March 13, 2013 > > New bee is welcome to join in the team > > > > For more information, please visit https://fedoraproject.org/wiki/FWN > > > > -Rashadul Islam > > 0x5557BFAC -- Thanks, Warm regards, Ankur: "FranciscoD" Please only print if necessary. Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG http://fedoraproject.org/wiki/User:Ankursinha http://dodoincfedora.wordpress.com/

11 years, 2 months

Re: Typo in Fedora CLA

by Darren VanBuren

On 1/24/2009 8:11 AM, Craig Thomas wrote: > 2009/1/24 Christoph Wurm<wurm.ch(a)googlemail.com>: > >> Dear Website Maintainers, >> >> apparently there are very few people who actually read the Fedora >> Contributor License Agreement. >> (https://admin.fedoraproject.org/accounts/cla/) >> There is a typing error in point five misspelling "patents" as "atents". >> Quite embarrassing for a legal agreement, but it should be easy to fix. >> >> > > Who here has access to the FAS git repo? > > diff --git a/fas/templates/cla/cla.html b/fas/templates/cla/cla.html > index 865f586..e0269d9 100644 > --- a/fas/templates/cla/cla.html > +++ b/fas/templates/cla/cla.html > @@ -65,7 +65,7 @@ > You represent that you are legally entitled to grant the above > license. If your employer(s) has rights to intellectual property that > you create that includes your Contributions, you represent that you > have received permission to make Contributions on behalf of that > employer, that your employer has waived such rights for your > Contributions to the Project, or that your employer has executed a > separate Corporate CLA with the Project. > </li> > <li> > - You represent that each of your Contributions is your original > creation (see section 7 for submissions on behalf of others). You > represent that your Contribution submission(s) include complete > details of any third-party license or other restriction (including, > but not limited to, related copyright, atents and trademarks) of which > you are personally aware and which are associated with any part of > your Contribution. > + You represent that each of your Contributions is your original > creation (see section 7 for submissions on behalf of others). You > represent that your Contribution submission(s) include complete > details of any third-party license or other restriction (including, > but not limited to, related copyright, patents and trademarks) of > which you are personally aware and which are associated with any part > of your Contribution. > </li> > <li> > You are not expected to provide support for your Contributions, > except to the extent you desire to provide support. You may provide > support for free, for a fee, or not at all. Your Contributions are > 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 NON-INFRINGEMENT, MERCHANTABILITY, or > FITNESS FOR A PARTICULAR PURPOSE. > diff --git a/fas/templates/cla/cla.txt b/fas/templates/cla/cla.txt > index 37f7caf..1439d80 100644 > --- a/fas/templates/cla/cla.txt > +++ b/fas/templates/cla/cla.txt > @@ -119,7 +119,7 @@ ${person.postal_address} > You represent that your Contribution submission(s) include > complete details of any third-party license or other > restriction (including, but not limited to, related copyright, > - atents and trademarks) of which you are personally aware and > + patents and trademarks) of which you are personally aware and > which are associated with any part of your Contribution. > > 6. You are not expected to provide support for your Contributions, > > Has this change taken effect on the Wiki? I may have git access, but I've never set it up.

15 years, 4 months

Re: [Design-team] How to get ticket for contributing in design-team

by Ankur Sinha

On Wed, 2012-08-29 at 00:55 +0530, umesh agarwal wrote: > Hello, <snip> > > I am really interested in design team works but i don't know how to > participate.How to get ticket for a design task. > > So I request design team to please help me out, so that I can > contribute my work. Hi Umesh, It's great to see more folks trying to contribute! If you haven't already, please go through the wiki page on "Join the design team" here[1]. The "getting started" section tells you how to find tickets (hint: look at point 5, but don't skip the others!) If you have more queries, please ask. We are delighted to have you here and will be even *more* delighted to help you become a permanent design team contributor! -- Thanks, Warm regards, Ankur: "FranciscoD" Please only print if necessary. Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG http://fedoraproject.org/wiki/User:Ankursinha http://dodoincfedora.wordpress.com/

11 years, 9 months

Re: [Fedora-join] Fwd: getting start contributing

by Ankur Sinha

On Tue, 2013-01-29 at 01:17 +0530, Asanka Nissanka wrote: > Hi Hello Asanka! > I am a computer engineering undergraduate at university of Peradeniya, > Sri Lanka. And I am also an open source enthusiast who loves linux > most. So i am looking forward to contribute fedora. And i am so > grateful if somebody can tell me where should i start. Welcome to the Fedora community! It's great to get to know you! At Fedora, different members of the community contribute to different areas that keep us going. The various areas are described here: https://fedoraproject.org/wiki/Join As a first task, I'd suggest you go through the page and understand the various tasks. You can then pick what you want to work on and get started. If you have any more queries, you can drop us another email. The Sri Lanka community is very active in Fedora. Danishka works quite a bit on Hanthana which he uses for education in Sri Lanka, Buddhike works with FAmSCo to help Ambassadors carry out their tasks. You're most welcome to join us at the APAC ambassador's meeting on the IRC this Saturday and introduce yourself to everyone. Please see the following link for details: http://lists.fedoraproject.org/pipermail/ambassadors/2013-January/020801.... Do drop us an email if you have any specific queries. We'll be happy to help you get started in whatever way we can. -- Thanks, Warm regards, Ankur: "FranciscoD" Please only print if necessary. Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG http://fedoraproject.org/wiki/User:Ankursinha http://dodoincfedora.wordpress.com/

11 years, 4 months

[commops] Re: Introduction email

by Tummala Dhanvi

On Mon, Aug 1, 2016 at 4:22 PM, Kanika Murarka <kmurarka(a)redhat.com> wrote: > Hello, > > My name is Kanika Murarka. I have been contribute to Fedora QA and joined as an intern at Red Hat Bangalore for the same. I have been actively involved to engage more women in tech. I have been contributing to FOSS for last 2 yrs and I would like to contribute to community operations in Fedora. Hello Kanika, Good to know that you are already contributing to the Fedora QA via RedHat and also have prior open source contributions. To join the CommOps (community operations) you might want to first look at CommOps wiki page[0] to get a brief understanding of how the CommOps works and follow the steps at Join page[1] As Mani mentioned you might also want to join the Fedora Women and Diversity. Hope to see you around. [0]https://fedoraproject.org/wiki/CommOps [1]https://fedoraproject.org/wiki/CommOps/Join -- Regards Tummala Dhanvi https://www.dhanvi.org "Only thing that can never be 'RE-CYCLED' is 'WASTED TIME' ".

7 years, 10 months

releng pushed to truecommons (master). "truecommons fails to build from source: https://bugzilla.redhat.com/show_bug.cgi?id=1676160"

by notifications＠fedoraproject.org

Notification time stamped 2019-08-08 16:46:25 UTC From 1a8c5d8e1384b9d73c941df186f22ade25885f68 Mon Sep 17 00:00:00 2001 From: Fedora Release Engineering <releng(a)fedoraproject.org> Date: Aug 08 2019 16:46:20 +0000 Subject: truecommons fails to build from source: https://bugzilla.redhat.com/show_bug.cgi?id=1676160 --- diff --git a/.gitignore b/.gitignore deleted file mode 100644 index 9e1a394..0000000 --- a/.gitignore +++ /dev/null @@ -1,4 +0,0 @@ -/truecommons-2.3.3.tar.gz -/*.rpm -/.*/ -/*/ diff --git a/dead.package b/dead.package new file mode 100644 index 0000000..93607de --- /dev/null +++ b/dead.package @@ -0,0 +1 @@ +truecommons fails to build from source: https://bugzilla.redhat.com/show_bug.cgi?id=1676160 diff --git a/eclipse-1.0.txt b/eclipse-1.0.txt deleted file mode 100644 index 16cc69a..0000000 --- a/eclipse-1.0.txt +++ /dev/null @@ -1,87 +0,0 @@ -Eclipse Public License - v 1.0 - -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. diff --git a/sources b/sources deleted file mode 100644 index 0205b97..0000000 --- a/sources +++ /dev/null @@ -1 +0,0 @@ -c1bcb70fa6305e62a39e2fba1eabd4a2 truecommons-2.3.3.tar.gz diff --git a/truecommons.spec b/truecommons.spec deleted file mode 100644 index daa0a20..0000000 --- a/truecommons.spec +++ /dev/null @@ -1,222 +0,0 @@ -Name: truecommons -Version: 2.3.3 -Release: 17%{?dist} -Summary: TrueCommons -License: EPL -URL: https://%{name}.java.net - -# hg clone https://hg.java.net/hg/truecommons~v1 && cd truecommons~v1/ -# hg archive -r truecommons-2.3.3 truecommons-2.3.3.tar.gz -X ".hg*" -Source0: %{name}-%{version}.tar.gz -Source1: eclipse-1.0.txt -BuildArch: noarch - -BuildRequires: maven-local -BuildRequires: mvn(ch.qos.logback:logback-classic) -BuildRequires: mvn(net.java.truecommons:truecommons-parent:pom:) -BuildRequires: mvn(org.mockito:mockito-core) -BuildRequires: mvn(org.jsr-305:jsr-305:pom:) -BuildRequires: mvn(org.netbeans:jemmy) -BuildRequires: mvn(com.google.code.findbugs:annotations) - -%description -Common components for open source projects - -%package javadoc -Summary: Javadoc for %{name} - -%description javadoc -API documentation for %{name}. - -%package annotations -Summary: TrueCommons Annotations - -%description annotations -Provides common annotations with processors. You should use -the scope "provided" when adding this module as a dependency. - -%package cio -Summary: TrueCommons Container I/O - -%description cio -Provides container I/O components. - -%package io -Summary: TrueCommons I/O - -%description io -Provides common I/O components. - -%package jmx -Summary: TrueCommons JMX - -%description jmx -Provides service locators and components for safely -interfacing with JMX in a library module. - -%package key -Summary: TrueCommons KeyManager - -%description key -KeyManager modules provide secret key management. - -%package key-console -Summary: TrueCommons KeyManager Console - -%description key-console -Prompts the user for passwords via a console based dialog, if available. - -%package key-default -Summary: TrueCommons KeyManager Default - -%description key-default -The KeyManager implementation in this module fails to resolve any keys. -Its priority is set to Integer.MIN_VALUE, so any other KeyManager -module on the class path will take precedence. - -%package key-disable -Summary: TrueCommons KeyManager Disable - -%description key-disable -Putting this module on the class path effectively disables any key -management, regardless of any other KeyManager module which may be present -on the class path. - -%package key-hurlfb -Summary: TrueCommons KeyManager HurlingWindowFeedback - -%description key-hurlfb -Provides visible and audible feedback by hurling the Swing -based dialog whenever the users enters a wrong password. - -%package key-spec -Summary: TrueCommons KeyManager Specification - -%description key-spec -Specifies a pluggable API for key management. - -%package key-swing -Summary: TrueCommons KeyManager Swing - -%description key-swing -Prompts the user for passwords via a Swing based dialog, if available. - -%package logging -Summary: TrueCommons Logging - -%description logging -Provides a simple adapter to add support for localized messages to SLF4J. - -%package services -Summary: TrueCommons Services - -%description services -Provides service location which is designed to work well in both JEE -and OSGi environments and perfectly fits the dependency injection idiom -with support for JSR 330. - -%package shed -Summary: TrueCommons Shed - -%description shed -Hosts small but useful tools and utilities that didn't fit anywhere else. - -%prep -%setup -q - -cp %{SOURCE1} . - -# Add jsr-305 as dependency for annotations and io -%pom_add_dep org.jsr-305:ri - -# Pull our scala stuff used for tests -%pom_remove_dep org.scala-lang:scala-library %{name}-io -rm -rf %{name}-io/src/{main,test}/scala -rm -rf %{name}-shed/src/test/scala -rm -rf %{name}-cio/src/test/scala -rm -rf %{name}-logging/src/test/scala -rm -rf %{name}-jmx/src/test/scala -rm -rf %{name}-services/src/test/scala - -#Disable macosx specific module -%pom_disable_module %{name}-key-macosx %{name}-key - -%build -%mvn_build -s - -%install -%mvn_install - -%files -f .mfiles-%{name} -%dir %{_javadir}/%{name} -%doc eclipse-1.0.txt - -%files javadoc -f .mfiles-javadoc -%doc eclipse-1.0.txt - -%files annotations -f .mfiles-%{name}-annotations -%doc eclipse-1.0.txt - -%files io -f .mfiles-%{name}-io -%doc eclipse-1.0.txt - -%files shed -f .mfiles-%{name}-shed -%doc eclipse-1.0.txt - -%files logging -f .mfiles-%{name}-logging -%doc eclipse-1.0.txt - -%files cio -f .mfiles-%{name}-cio -%files jmx -f .mfiles-%{name}-jmx -%files key -f .mfiles-%{name}-key -%files key-console -f .mfiles-%{name}-key-console -%files key-default -f .mfiles-%{name}-key-default -%files key-disable -f .mfiles-%{name}-key-disable -%files key-hurlfb -f .mfiles-%{name}-key-hurlfb -%files key-spec -f .mfiles-%{name}-key-spec -%files key-swing -f .mfiles-%{name}-key-swing -%files services -f .mfiles-%{name}-services - -%changelog -* Sat Jul 27 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.3-17 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild - -* Sun Feb 03 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.3-16 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild - -* Sat Jul 14 2018 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.3-15 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild - -* Fri Feb 09 2018 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.3-14 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild - -* Thu Jul 27 2017 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.3-13 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild - -* Sat Feb 11 2017 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.3-12 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild - -* Fri Feb 05 2016 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.3-11 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild - -* Fri Jun 19 2015 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org> - 2.3.3-10 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild - -* Tue Jun 10 2014 Gerard Ryan <galileo(a)fedoraproject.org> - 2.3.3-9 -- Add BR on logback-classic -- Fix BR on jsr-305 and truecommons-parent - -* Sun Jun 08 2014 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org> - 2.3.3-7 -- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild - -* Fri Feb 28 2014 Gerard Ryan <galileo(a)fedoraproject.org> - 2.3.3-6 -- RHBZ-1068569: Switch to java-headless requires - -* Sat Dec 28 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.3.3-5 -- Rebuild with new findbugs-2.0.3 - -* Mon Nov 18 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.3.3-2 -- RHBZ-1031437: Modifications for review request - -* Sat Nov 16 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.3.3-1 -- Initial package https://src.fedoraproject.org/rpms/truecommons/c/1a8c5d8e1384b9d73c941df1...

4 years, 10 months

Re: Self-introduction: bithakr

by Lailah

Hello Aidan! Welcome here and sorry for the late response. Somehow, your message got lost in the crowd. Feel free to start contributing, asking questions, etc. Looking forward to see your contributions! Cheers and happy holidays, Sylvia On 23/12/16 01:05, Aidan Hunt wrote: > Hello Fedora Docs Project, > > My name is Aidan Hunt and I am a student at the Early College at Guilford in NC, United States. I've been coding since I was 9. I started working with C#.NET on WinDoze, then I moved to a free software workflow. I am fluent in C and to a somewhat lesser extent C++, and I am working on some new projects in Java as well as some Android stuff. > > When I'm not on Fedora, I use ArchLinux. You can find me at Github, Gitlab, Twitter, and a few other places under this username (bithakr). > > I have worked with wikis for several years. I am an extended confirmed user, a rollbacker, and a pending changes review with over 1,706 edits @ Wikipedia-en (User:Blackhat999). I have just started contributing to the eLinux.org wiki, and I am helping with the documentation of quick-back (https://github.com/penguinsnail/quick-back), a small rsync backup script created by a friend. > > I am mostly interested in contributing to the FedoraProject Wiki (for example, today I noticed that some one the Android Dev workflow articles were a little out of date), but I might also have some time to work on docs for particular software programs. > > As far as GPG goes, my key is (on pgp.mit.edu): > > pub 4096R/FC0E03D0 2016-08-20 HaKr <bit(a)hakr.me> > HaKr <admin(a)hakr.me> > HaKr <hunta1(a)guilford.edu> > > I look forward to contributing to the project. > > Happy hacking, > > ~bithakr > _______________________________________________ > docs mailing list -- docs(a)lists.fedoraproject.org > To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org

7 years, 5 months

Re: Request for Comments: Fedora Project Contributor Agreement Draft (Replacement for Fedora Individual Contributor License Agreement)

by Tom Callaway

On 04/22/2010 01:45 AM, Sir Gallantmon (ニール・ゴンパ) wrote: > But it should be explicitly stated anyway. Legalese isn't English. > Note: IANAL Well, there is nothing in the FPCA that says we will accept or use your contribution, even if it is acceptably licensed. :) I'm not sure there is a lot of merit in writing out all of the possible permutations of what consists of a contribution that Fedora will accept, outside of licensing. For example, stating "no binaries", wouldn't be true, as we might have a situation where we would have a bootstrapped binary contributed along with the source, but for bootstrapping reasons, needs to be included as a starter. Stating "no binaries without matching source" wouldn't be true either, as content isn't always required to have matching source (what is the "source" for a PNG file?). This road leads to pages and pages of conditionals and cases, which are inevitably going to be incomplete, and to which we will need to make revisions overtime, and everytime we make a revision here, we'll have to open a new discussion period on a new draft which has to clear through Red Hat Legal, and then we have to revoke the old FPCA for everyone and have everyone sign the new one. We're desperately trying to avoid that by keeping it as simple and direct as possible. We already have separate guidelines which we enforce independent of the FPCA that say: "All software in Fedora must be under licenses in the Fedora licensing list." (https://fedoraproject.org/wiki/Licensing#Overview) and "All program binaries and program libraries included in Fedora packages must be built from the source code that is included in the source package." (... and several notable paragraphs documenting exceptions there) (https://fedoraproject.org/wiki/Packaging/Guidelines#No_inclusion_of_pre-b...) These guidelines are much easier for us to change in the format that they exist in today. When the FPCA is boiled down, it amounts to this: You, the individual agreeing to the FPCA is promising Fedora (and Red Hat) that: * If you aren't the copyright holder for a work that you are submitting to Fedora as a contribution, that you have received appropriate permission from the copyright holder(s) of that work to submit it to Fedora (and if that work is under a Fedora acceptable license, that counts as appropriate permission.) [Clause 1] * If you are the copyright holder for a work that you are submitting to Fedora as a contribution, but you have not put a license on it, you are agreeing to let Fedora use it under specific, defined Fedora Acceptable licenses (MIT if it is code, CC-BY-SA with section 4d waived if it is content) [Clause 3] * You agree to give Fedora the right to change the default licenses for unlicensed contributions, from the list of Fedora Acceptable licenses, and have that new license also apply to your contributions. [Clause 3] The Fedora Project is promising to You (and everyone) that: * If a contribution comes to us under a Fedora acceptable license, and we decide to accept it, we will use it under the terms of that license. [Clause 2] ****** And to be honest, we really didn't want to overreach with the FPCA. Thats all we really felt that we needed to have you explicitly agree to. ~spot

14 years, 1 month

[commops] Re: Introduction: Rutvik Kshirsagar

by Justin W. Flory

On 09/30/2016 07:15 AM, Rutvik Kshirsagar wrote: > Hello everyone! > > My name is Rutvik Kshirsagar. I am from India and I am pursuing my > Bachelors of Engineering in the field of Computer Science. > > I am interested in development and contributing to open source and this > is my first time contribution to open source. > > I have achieved 3 Red Hat certification i.e I am entitled with RHCE, > RHCSA (RHEL 7, OpenStack). > I am interested in contributing to storytelling, wiki, badges. > > > Regards, > Rutvik Kshirsagar > IRC:rutvik > rutksh(a)gmail.com <mailto:rutksh@gmail.com> > Greetings, Rutvik! Welcome to the CommOps mailing list. Happy to have you join us here. :) Awesome to hear that this is your first time contributing to open source! It's a big step into something awesome, and I'm glad we're able to help share that experience with you. Should you have any questions at any point, don't hesitate to reach out and ask. As far as your development interests go, there are plenty of areas in the project that might interest you. I encourage you to explore these areas by going to the "What can I do for Fedora?" website to see just what all there is in Fedora to check out. http://whatcanidoforfedora.org/ As far as storytelling, wiki, and badges go, there are also plenty of ways for you to contribute to these areas. Storytelling is definitely one of the important parts of what we do. It's about delivering the message about what's happening across Fedora among our own community and sharing it with other communities as well. Writing articles for the Community Blog is just one example of this, and it's a great way to contribute if you're participating in any local events or if you see news about something interesting happening in Fedora. Badges is one tool we use to help improve the on-boarding experience for new contributors getting involved with the project. One thing I encourage you to explore a bit first is the proposal for the "Bootstrapped!" series of badges. These will help give you a good introduction to Fedora and also introduce you to what Fedora Badges is. Here are some helpful links for you to follow in regards to that: https://fedorahosted.org/fedora-badges/ticket/409 https://fedoraproject.org/wiki/CommOps/Join Hope this is enough to help get you started in the right direction. :) Like I said earlier, if you have any questions, don't hesitate to reach out here on the mailing list. We're more than happy to help you get started or get through any blockers. As an extra note, we also have weekly meetings on Tuesdays at 16:30 UTC (I believe this is 10pm IST). If you are available at this time, feel free to hop in the #fedora-meeting channel on freenode IRC and participate in the meeting. Thanks for introducing yourself, and hope to catch you around in Fedora! -- Cheers, Justin W. Flory jflory7(a)gmail.com

7 years, 8 months

Search results for query "contribute to wiki"