Change Details

The old policy for contributing to prototype applications stated that changes to prototype applications was not allowed //with rare exceptions//. But today in Phorge, there are a good number of patches and contributions to prototype applications (including but not limited to {PHID-APPS-PhabricatorCalendarApplication} and {PHID-APPS-PhabricatorPackagesApplication}). We are a community accepting more patches than Phabricator, as Phacility did not prioritize contributions to prototypes at all and relied on SaaS and paid priorization. == The Phabricator-Era Policy == >No Prototype Changes >==================== > >With rare exceptions, we do not accept patches for prototype applications for the same reasons that we don't accept feature requests or bug reports. To learn more about prototype applications, see @{article:User Guide: Prototype Applications}. == Propsed Policy == >>! In D25905#24435, @valerio.bozzolan wrote: > Prototype Changes > ================= > > We generally advise against submitting patches for prototype applications, as they are often subject to significant changes and may not be widely adopted and may need extra care from rare users who are particularly familiar with them. For the same reasons, we also discourage feature requests or bug reports for these applications, unless you are very familiar with their original design and their original workflows. As always, you can [[/ponder/ | open a question in Ponder]] instead. To learn more about prototype applications, see > @{article:User Guide: Prototype Applications}. == What We Agree On == - Users must be familiar with prototypes' orginal design and workflows - User can ask about prototypes in here Ponder.

The old policy for contributing to prototype applications stated that changes to prototype applications was not allowed //with rare exceptions//. But today in Phorge, there are a good number of patches and contributions to prototype applications (including but not limited to {PHID-APPS-PhabricatorCalendarApplication} and {PHID-APPS-PhabricatorPackagesApplication}). We are a community accepting more patches than Phabricator, as Phacility did not prioritize contributions to prototypes at all and relied on SaaS and paid priorization. == The Phabricator-Era Policy == >No Prototype Changes >==================== > >With rare exceptions, we do not accept patches for prototype applications for the same reasons that we don't accept feature requests or bug reports. To learn more about prototype applications, see @{article:User Guide: Prototype Applications}. == Propsed Policy == >>! In D25905#24435, @valerio.bozzolan wrote: > Prototype Changes > ================= > > We generally advise against submitting patches for prototype applications, as they are often subject to significant changes and may not be widely adopted and may need extra care from rare users who are particularly familiar with them. For the same reasons, we also discourage feature requests or bug reports for these applications, unless you are very familiar with their original design and their original workflows. As always, you can [[/ponder/ | open a question in Ponder]] instead. To learn more about prototype applications, see > @{article:User Guide: Prototype Applications}. == What We Agree On == - Users must be familiar with prototypes' orginal design and workflows - User can ask about prototypes in here / Ponder.

The old policy for contributing to prototype applications stated that changes to prototype applications was not allowed //with rare exceptions//. But today in Phorge, there are a good number of patches and contributions to prototype applications (including but not limited to {PHID-APPS-PhabricatorCalendarApplication} and {PHID-APPS-PhabricatorPackagesApplication}). We are a community accepting more patches than Phabricator, as Phacility did not prioritize contributions to prototypes at all and relied on SaaS and paid priorization. == The Phabricator-Era Policy == >No Prototype Changes >==================== > >With rare exceptions, we do not accept patches for prototype applications for the same reasons that we don't accept feature requests or bug reports. To learn more about prototype applications, see @{article:User Guide: Prototype Applications}. == Propsed Policy == >>! In D25905#24435, @valerio.bozzolan wrote: > Prototype Changes > ================= > > We generally advise against submitting patches for prototype applications, as they are often subject to significant changes and may not be widely adopted and may need extra care from rare users who are particularly familiar with them. For the same reasons, we also discourage feature requests or bug reports for these applications, unless you are very familiar with their original design and their original workflows. As always, you can [[/ponder/ | open a question in Ponder]] instead. To learn more about prototype applications, see > @{article:User Guide: Prototype Applications}. == What We Agree On == - Users must be familiar with prototypes' orginal design and workflows - User can ask about prototypes in here / Ponder.