[RULES] READ FIRST BEFORE PUBLISHING YOUR DEVELOPMENTs

Search This thread

deathnotice01

Senior Member
Feb 19, 2012
8,328
3,136
Cebu
android-security-avast.jpg
Developer Decorum and Conduct



1.) How is Android Licensed?
Android is open source and Google releases the code under the Apache License. This open source code and permissive licensing allows the software to be freely modified and distributed by device manufacturers, wireless carriers and enthusiast developers.
Full version here
Read Apache Licence here


2.) What is Open-Source?
open source refers to a program in which the source code is available to the general public for use and/or modification from its original design. Open source code is typically created as a collaborative effort in which programmers improve upon the code and share the changes within the community.
Read Open-Sourcing here


3.) Too many big words, what does this mean exactly?
Everytime you develop for the android-software you are bound by the GPL, Apache license and the XDA forum rules
See full GPL Licence here


4.) What must I do before publishing my work?
Review your work and see if it violates any of the following:​

XDA Forum Rules #12
Using the Work of others
If you are developing something that is based on the work of another Member, you MUST first seek their permission, and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails then you may contact a moderator with clear evidence that the work was created by you.

Convincing evidence will result in copied work being removed. If there is no clear evidence you created the work then in the spirit of sharing all work will remain posted on the forums.

As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by the dev or freely share it. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie allowing certain people to use it and not others). Should the dev decide to start sharing the work with others, the work automatically becomes fair game for all to use.

In regards to permissions, same rules remain for this but if permission was already given, unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under severe circumstances.

In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.

These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.

Ask permission before using other's work, no matter how small it is (a .png file or a xml code), please secure all nessesarry permits from the original author before publishing

Tips
Create your own license, disclaimer and warranty notice


Protect your work by creating your own license and publishing them together with your work, remember this is your work and you have all the right to secure it at will and on your behalf, just make sure you clearly specify your license, disclaimer and warranty.

Open-GPL Licence Sec. 5-6
Publishing your sources, and providing notice of modification
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.

After securing the permits if in case your project is a derivative or is based upon another project, you must publish and indicate it in a conspicuous and clear place within your post or work together with it's sources,

if in case of a original work, you must indicate the sources in a conspicuous and clear place within your post or work

XDA Forum Rules #6
Do not post warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community

Don't Include Paid Apps versions on your work, Remember not all app developers do it for a hobby, sometimes they rely on app purchases for feed their kids, pay their bills and get their life ahead,

XDA Forum Rules #13
Advertising and Income Generation
Commercial advertising, advertising referral links, pay per click links and other income generating methods are forbidden. Do not use xda-developers as a means to make money.

Don't post your link to redirect a pay-per-click (e.g adfly, etc) website
Link to the XDA Forum Rules


5.) The original author declined my permission to use his work or he is not responding, What shall i do?
If in case the author has declined to provide permissions to secure usage of his work. then you are unable to publish it in XDA, you are however free to use it for your own device without sharing the source.

If in case author was unable to respond, PM the moderator to settle this issue and wait for a "GO" signal to publish your work.


6.) A person accused me of stealing his work, What should I do to defend myself?
PM the accusor to disscuss with him the matter at hand, however if you are unable to negotiate a concensus with the accusor, then PM a moderator to settle your disputes DON'T FIGHT WITHIN THE DEVELOPMENT THREAD, and wait for the moderators to finish their investigation and undergo a conclusion on the matter


7.) Does #4 apply to porting roms, apps, from another device?
 
Last edited:

deathnotice01

Senior Member
Feb 19, 2012
8,328
3,136
Cebu
I Guess Cm7 doesn't needs permissions, it's also open source, we need to provide the credits properly.. :)

That's what I have seen so far.. ;)

depends,
if it is originally compiled from source then you need to indicate the sources and publish them in pursuant to GPL sect. 5-6,

if work is a port then credits should be properly given also the permission from original dev
 

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    android-security-avast.jpg
    Developer Decorum and Conduct



    1.) How is Android Licensed?
    Android is open source and Google releases the code under the Apache License. This open source code and permissive licensing allows the software to be freely modified and distributed by device manufacturers, wireless carriers and enthusiast developers.
    Full version here
    Read Apache Licence here


    2.) What is Open-Source?
    open source refers to a program in which the source code is available to the general public for use and/or modification from its original design. Open source code is typically created as a collaborative effort in which programmers improve upon the code and share the changes within the community.
    Read Open-Sourcing here


    3.) Too many big words, what does this mean exactly?
    Everytime you develop for the android-software you are bound by the GPL, Apache license and the XDA forum rules
    See full GPL Licence here


    4.) What must I do before publishing my work?
    Review your work and see if it violates any of the following:​

    XDA Forum Rules #12
    Using the Work of others
    If you are developing something that is based on the work of another Member, you MUST first seek their permission, and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails then you may contact a moderator with clear evidence that the work was created by you.

    Convincing evidence will result in copied work being removed. If there is no clear evidence you created the work then in the spirit of sharing all work will remain posted on the forums.

    As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by the dev or freely share it. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie allowing certain people to use it and not others). Should the dev decide to start sharing the work with others, the work automatically becomes fair game for all to use.

    In regards to permissions, same rules remain for this but if permission was already given, unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under severe circumstances.

    In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.

    These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.

    Ask permission before using other's work, no matter how small it is (a .png file or a xml code), please secure all nessesarry permits from the original author before publishing

    Tips
    Create your own license, disclaimer and warranty notice


    Protect your work by creating your own license and publishing them together with your work, remember this is your work and you have all the right to secure it at will and on your behalf, just make sure you clearly specify your license, disclaimer and warranty.

    Open-GPL Licence Sec. 5-6
    Publishing your sources, and providing notice of modification
    5. Conveying Modified Source Versions.
    You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

    a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
    b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
    c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
    d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
    A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

    6. Conveying Non-Source Forms.
    You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

    a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
    b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
    c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
    d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
    e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.

    After securing the permits if in case your project is a derivative or is based upon another project, you must publish and indicate it in a conspicuous and clear place within your post or work together with it's sources,

    if in case of a original work, you must indicate the sources in a conspicuous and clear place within your post or work

    XDA Forum Rules #6
    Do not post warez.
    If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community

    Don't Include Paid Apps versions on your work, Remember not all app developers do it for a hobby, sometimes they rely on app purchases for feed their kids, pay their bills and get their life ahead,

    XDA Forum Rules #13
    Advertising and Income Generation
    Commercial advertising, advertising referral links, pay per click links and other income generating methods are forbidden. Do not use xda-developers as a means to make money.

    Don't post your link to redirect a pay-per-click (e.g adfly, etc) website
    Link to the XDA Forum Rules


    5.) The original author declined my permission to use his work or he is not responding, What shall i do?
    If in case the author has declined to provide permissions to secure usage of his work. then you are unable to publish it in XDA, you are however free to use it for your own device without sharing the source.

    If in case author was unable to respond, PM the moderator to settle this issue and wait for a "GO" signal to publish your work.


    6.) A person accused me of stealing his work, What should I do to defend myself?
    PM the accusor to disscuss with him the matter at hand, however if you are unable to negotiate a concensus with the accusor, then PM a moderator to settle your disputes DON'T FIGHT WITHIN THE DEVELOPMENT THREAD, and wait for the moderators to finish their investigation and undergo a conclusion on the matter


    7.) Does #4 apply to porting roms, apps, from another device?
    7
    Stickied:)

    Personally, I've decided to sticky this. It has a decent amount of valuable information and this thread makes it a lot more easily accessible and in one place for potential developers to be made aware of.

    Great, informative thread.
    2
    reserved for FAQ's and appendixes
    1
    reserved for samples and others