Discussion:
[Framework-Team] PLIP Process
Ramon Navarro Bosch
2015-11-23 16:04:53 UTC
Permalink
Hey as I can remember we decided to stop dev.plone.org as a PLIP platform
and decided to use GitHub Issues with PLIP label. Isn't that right ? Kim
was asking for information about that on the GH and, besides
buildout.coredev/docs info is outdated, I couldn't find the label on the
Products.CMFPlone issue tracker.

What was the decided decision about PLIP process ?

R
Johannes Raggam
2015-11-24 13:54:15 UTC
Permalink
Let's discuss that at the meeting. Anyways, my position:


Yes, there was a decision to give up dev.plone.org and use github issues
instead. IIRC, maurits' already made some kind-of plips:

https://github.com/plone/Products.CMFPlone/issues/1008
https://github.com/plone/Products.CMFPlone/issues/1198

I think we should use dev.plone.org as entry point for developers, where
the most important information/links can be found. e.g. "about the PLIP
process", "PLIP template", "code style guide", "how to contribute".

Regarding the label, the label "04 type: enhancement" comes close to be
a PLIP label, but we need a specific one.

We should keep our Google docs document for managing PLIPs, because
github doesn't offer enough features to replace that (voting,
conditional labels only valid for PLIPs, etc).


Cheers,
Johannes
Post by Ramon Navarro Bosch
Hey as I can remember we decided to stop dev.plone.org
<http://dev.plone.org> as a PLIP platform and decided to use GitHub
Issues with PLIP label. Isn't that right ? Kim was asking for
information about that on the GH and, besides buildout.coredev/docs info
is outdated, I couldn't find the label on the Products.CMFPlone issue
tracker.
What was the decided decision about PLIP process ?
R
_______________________________________________
Framework-Team mailing list
https://lists.plone.org/mailman/listinfo/plone-framework-team
Johannes Raggam
2015-11-24 13:59:02 UTC
Permalink
Sorry, next FWT is December 1st, not today.
Post by Johannes Raggam
Yes, there was a decision to give up dev.plone.org and use github issues
https://github.com/plone/Products.CMFPlone/issues/1008
https://github.com/plone/Products.CMFPlone/issues/1198
I think we should use dev.plone.org as entry point for developers, where
the most important information/links can be found. e.g. "about the PLIP
process", "PLIP template", "code style guide", "how to contribute".
Regarding the label, the label "04 type: enhancement" comes close to be
a PLIP label, but we need a specific one.
We should keep our Google docs document for managing PLIPs, because
github doesn't offer enough features to replace that (voting,
conditional labels only valid for PLIPs, etc).
Cheers,
Johannes
Post by Ramon Navarro Bosch
Hey as I can remember we decided to stop dev.plone.org
<http://dev.plone.org> as a PLIP platform and decided to use GitHub
Issues with PLIP label. Isn't that right ? Kim was asking for
information about that on the GH and, besides buildout.coredev/docs info
is outdated, I couldn't find the label on the Products.CMFPlone issue
tracker.
What was the decided decision about PLIP process ?
R
_______________________________________________
Framework-Team mailing list
https://lists.plone.org/mailman/listinfo/plone-framework-team
Ramon Navarro Bosch
2015-11-24 14:52:32 UTC
Permalink
What about using this :
http://issuetemplate.com/#/plone/Products.CMFPlone/PLIP

I would disconect dev.plone.org and use the new plone.org (that is going to
be online soon) to add the info we have at

https://github.com/plone/buildout.coredev/tree/5.0/docs

Ramon
Post by Johannes Raggam
Sorry, next FWT is December 1st, not today.
Post by Johannes Raggam
Yes, there was a decision to give up dev.plone.org and use github issues
https://github.com/plone/Products.CMFPlone/issues/1008
https://github.com/plone/Products.CMFPlone/issues/1198
I think we should use dev.plone.org as entry point for developers, where
the most important information/links can be found. e.g. "about the PLIP
process", "PLIP template", "code style guide", "how to contribute".
Regarding the label, the label "04 type: enhancement" comes close to be
a PLIP label, but we need a specific one.
We should keep our Google docs document for managing PLIPs, because
github doesn't offer enough features to replace that (voting,
conditional labels only valid for PLIPs, etc).
Cheers,
Johannes
Post by Ramon Navarro Bosch
Hey as I can remember we decided to stop dev.plone.org
<http://dev.plone.org> as a PLIP platform and decided to use GitHub
Issues with PLIP label. Isn't that right ? Kim was asking for
information about that on the GH and, besides buildout.coredev/docs info
is outdated, I couldn't find the label on the Products.CMFPlone issue
tracker.
What was the decided decision about PLIP process ?
R
_______________________________________________
Framework-Team mailing list
https://lists.plone.org/mailman/listinfo/plone-framework-team
Jens W. Klein
2015-11-25 14:19:18 UTC
Permalink
After some discussion I introduced the label "03 type: feature" exactly
for plips.
After some discussion the more general word "feature" was preferred and
I renamed it (I first named it "03 type: plip", but after discussions
first at at community.plone.org and then at 2015 conference we renamed it).

Enhancement is a small change with no need to PLIP.
Post by Ramon Navarro Bosch
What about using this
: http://issuetemplate.com/#/plone/Products.CMFPlone/PLIP
I did not know about issuetemplate, thats really great! Gets a +1 by me.

If we decide to use issuetemplate I propose add a short note about it to
http://docs.plone.org/develop/coredev/docs/guidelines.html and the
longer explanation to http://docs.plone.org/develop/coredev/docs/plips.html
Post by Ramon Navarro Bosch
I would disconect dev.plone.org <http://dev.plone.org> and use the new
plone.org <http://plone.org> (that is going to be online soon) to add
the info we have at
https://github.com/plone/buildout.coredev/tree/5.0/docs
Afaik there were already some date announced (Dec.31st?) when
dev.plone.org will be shut down.

Jens
Post by Ramon Navarro Bosch
Ramon
Sorry, next FWT is December 1st, not today.
Post by Johannes Raggam
Yes, there was a decision to give up dev.plone.org
<http://dev.plone.org> and use github issues
Post by Johannes Raggam
https://github.com/plone/Products.CMFPlone/issues/1008
https://github.com/plone/Products.CMFPlone/issues/1198
I think we should use dev.plone.org <http://dev.plone.org> as
entry point for developers, where
Post by Johannes Raggam
the most important information/links can be found. e.g. "about the
PLIP
Post by Johannes Raggam
process", "PLIP template", "code style guide", "how to contribute".
Regarding the label, the label "04 type: enhancement" comes close
to be
Post by Johannes Raggam
a PLIP label, but we need a specific one.
We should keep our Google docs document for managing PLIPs, because
github doesn't offer enough features to replace that (voting,
conditional labels only valid for PLIPs, etc).
Cheers,
Johannes
Post by Ramon Navarro Bosch
Hey as I can remember we decided to stop dev.plone.org
<http://dev.plone.org>
Post by Johannes Raggam
Post by Ramon Navarro Bosch
<http://dev.plone.org> as a PLIP platform and decided to use GitHub
Issues with PLIP label. Isn't that right ? Kim was asking for
information about that on the GH and, besides
buildout.coredev/docs info
Post by Johannes Raggam
Post by Ramon Navarro Bosch
is outdated, I couldn't find the label on the Products.CMFPlone issue
tracker.
What was the decided decision about PLIP process ?
R
_______________________________________________
Framework-Team mailing list
https://lists.plone.org/mailman/listinfo/plone-framework-team
--
Klein & Partner KG, member of BlueDynamics Alliance
Franco Pellegrini
2015-11-25 14:39:52 UTC
Permalink
Post by Ramon Navarro Bosch
http://issuetemplate.com/#/plone/Products.CMFPlone/PLIP
I like this!
Post by Ramon Navarro Bosch
I would disconect dev.plone.org and use the new plone.org (that is going
to be online soon) to add the info we have at
https://github.com/plone/buildout.coredev/tree/5.0/docs
I would also disconnect dev.plone.org so it no longer points to the Trac
system, and instead (and I think this is what Johannes meant) would have
dev.plone.org to either be or look like a subsection of plone.org with all
the relevant information for Plone developers
Post by Ramon Navarro Bosch
Ramon
Cheers,
Franco
Eric Bréhault
2015-11-25 16:49:48 UTC
Permalink
+1 for http://issuetemplate.com/#/plone/Products.CMFPlone/PLIP
Post by Franco Pellegrini
Post by Ramon Navarro Bosch
http://issuetemplate.com/#/plone/Products.CMFPlone/PLIP
I like this!
Post by Ramon Navarro Bosch
I would disconect dev.plone.org and use the new plone.org (that is going
to be online soon) to add the info we have at
https://github.com/plone/buildout.coredev/tree/5.0/docs
I would also disconnect dev.plone.org so it no longer points to the Trac
system, and instead (and I think this is what Johannes meant) would have
dev.plone.org to either be or look like a subsection of plone.org with
all the relevant information for Plone developers
Post by Ramon Navarro Bosch
Ramon
Cheers,
Franco
_______________________________________________
Framework-Team mailing list
https://lists.plone.org/mailman/listinfo/plone-framework-team
Loading...