Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Wayne Beaton 

  
  
I start from a position of trusting committers to do the right
thing.

The problem with enforcement is that there are always corner cases
that cause everybody grief. I'd rather trust the committers to do
the right thing. This, along with revision management should get us
there.

Another thing that I'd like to add to the PMI is the ability to
subscribe to changes on any individual record. We could also
entertain automatic notification to the PL or all committers
whenever a record is changed. I generally don't like sending too
many emails, so we'll have to figure out how to strike a balance.

Wayne

On 03/15/2013 02:48 PM, Ed Willink
  wrote:


  
  Hi Wayne
  

The PMI is built on Drupal. Drupal is a content management
system.

There is a "Revision Information" tab at the bottom of the page
that you can use to create a new revision whenever you want.

I've been toying with the idea of creating a revision every time
the form is saved. Thoughts?
  
  That could tip the balance.
  
  For a project plan, what kind of freezing is in place? At present,
  and under the new system presumably I can just go back to the
  Helios plan and create a very different impression to users and
  not what was endorsed by the Release Review. CM at least
  demonstrates that I have done this.
  
  Perhaps the RR submissions should be tagged, and only EMO/PMC are
  able to move tags thereafter.
  
      Regards
  
          Ed Willink
  
  
  
  
  
  ___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
  Wayne Beaton
  Director of Open Source Projects, The Eclipse Foundation
  Learn about Eclipse
Projects
  
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Wayne Beaton 

  
  
Maybe try *tools*.windowbuilder? :-)


http://www.eclipse.org/projects/project-plan.php?projectid=tools.windowbuilder

This reminds me that the project-plan renderer is a terrible
time-sink any time that it needs to be fixed or rendering problems
need to be chased down. I'll likely deprecate it the next time it
causes trouble.

Wayne

On 03/15/2013 02:47 PM, Mark Russell
  wrote:


  Wayne:
when I go to http://www.eclipse.org/projects/project-plan.php?projectid=technology.windowbuilder
  I get a can not display page.  What do I have to do to get our
  project setup?
  
  

On Fri, Mar 15, 2013 at 2:33 PM, Wayne
  Beaton 
  wrote:
  
 The PMI is built on
  Drupal. Drupal is a content management system.
  
  There is a "Revision Information" tab at the bottom of the
  page that you can use to create a new revision whenever
  you want.
  
  I've been toying with the idea of creating a revision
  every time the form is saved. Thoughts?
  
  Wayne
  

  
  On 03/15/2013 02:29 PM, Ed Willink wrote:
  

  
  

   Hi

On 15/03/2013 18:18, Wayne Beaton wrote:

 How do I make that choice?
  
  Do you like editing XML and doing revision control
  in Git, or do you prefer to use a web form?

No, Yes (in a CM), only when it offers me CM.

So on balance I prefer the old way so that I have
CM.

   
How is the choice enforced? 
  
  It's not. I just need to see a plan either in the
  required XML format, or in the database. In the
  end, it's just a URL either way.
   
If there are two separate copies which is seen
by the user? 
  
  No. If you provide an XML file, then we'll render
  it the old-fashioned way from a link that we'll
  put on the review record. Maybe I should include
  an optional field on the release record to hold
  the link.

Please add that link.

    Regards

        Ed Willink



  


  ___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


  
   
-- 
  Wayne Beaton
  Director of Open Source Projects, The Eclipse Foundation
  Learn about Eclipse Projects
  
  


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

  





-- 
Mark R Russell
(724) 473-3140
  Software Engineer in Test
  Google Pittsburgh
  

  
  
  
  
  ___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
  Wayne Beaton
  Director of Open Source Projects, The Eclipse Foundation
  Learn about Eclipse
Projects
  
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Ed Willink 

  
  
Hi Wayne

  
  The PMI is built on Drupal. Drupal is a content management system.
  
  There is a "Revision Information" tab at the bottom of the page
  that you can use to create a new revision whenever you want.
  
  I've been toying with the idea of creating a revision every time
  the form is saved. Thoughts?

That could tip the balance.

For a project plan, what kind of freezing is in place? At present,
and under the new system presumably I can just go back to the Helios
plan and create a very different impression to users and not what
was endorsed by the Release Review. CM at least demonstrates that I
have done this.

Perhaps the RR submissions should be tagged, and only EMO/PMC are
able to move tags thereafter.

    Regards

        Ed Willink


  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Mark Russell 
Wayne:
when I go to
http://www.eclipse.org/projects/project-plan.php?projectid=technology.windowbuilderI
get a can not display page.  What do I have to do to get our project
setup?


On Fri, Mar 15, 2013 at 2:33 PM, Wayne Beaton  wrote:

>  The PMI is built on Drupal. Drupal is a content management system.
>
> There is a "Revision Information" tab at the bottom of the page that you
> can use to create a new revision whenever you want.
>
> I've been toying with the idea of creating a revision every time the form
> is saved. Thoughts?
>
> Wayne
>
>
> On 03/15/2013 02:29 PM, Ed Willink wrote:
>
> Hi
>
> On 15/03/2013 18:18, Wayne Beaton wrote:
>
> How do I make that choice?
> Do you like editing XML and doing revision control in Git, or do you
> prefer to use a web form?
>
> No, Yes (in a CM), only when it offers me CM.
>
> So on balance I prefer the old way so that I have CM.
>
>
> How is the choice enforced?
>
> It's not. I just need to see a plan either in the required XML format, or
> in the database. In the end, it's just a URL either way.
>
>
> If there are two separate copies which is seen by the user?
>
> No. If you provide an XML file, then we'll render it the old-fashioned way
> from a link that we'll put on the review record. Maybe I should include an
> optional field on the release record to hold the link.
>
> Please add that link.
>
> Regards
>
> Ed Willink
>
>
> ___
> cross-project-issues-dev mailing 
> listcross-project-issues-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> --
> Wayne Beaton
> Director of Open Source Projects, The Eclipse 
> Foundation
> Learn about Eclipse Projects 
> [image: EclipseCon 2013] 
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>


-- 
Mark R Russell
(724) 473-3140
Software Engineer in Test
Google Pittsburgh
<<480x60.png>>___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Wayne Beaton 

  
  
The PMI is built on Drupal. Drupal is a content management system.

There is a "Revision Information" tab at the bottom of the page that
you can use to create a new revision whenever you want.

I've been toying with the idea of creating a revision every time the
form is saved. Thoughts?

Wayne

On 03/15/2013 02:29 PM, Ed Willink
  wrote:


  
  Hi
  
  On 15/03/2013 18:18, Wayne Beaton
wrote:
  
  

How do I make that choice? 
Do you like editing XML and doing revision control in Git, or do
you prefer to use a web form?
  
  No, Yes (in a CM), only when it offers me CM.
  
  So on balance I prefer the old way so that I have CM.
  
 
  How is the choice enforced? 

It's not. I just need to see a plan either in the required XML
format, or in the database. In the end, it's just a URL either
way.
 
  If there are two separate copies which is seen by the user? 

No. If you provide an XML file, then we'll render it the
old-fashioned way from a link that we'll put on the review
record. Maybe I should include an optional field on the release
record to hold the link.
  
  Please add that link.
  
      Regards
  
          Ed Willink
  
  
  
  ___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
  Wayne Beaton
  Director of Open Source Projects, The Eclipse Foundation
  Learn about Eclipse
Projects
  
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Ed Willink 

  
  
Hi

On 15/03/2013 18:18, Wayne Beaton
  wrote:


  
  How do I make that choice? 
  Do you like editing XML and doing revision control in Git, or do
  you prefer to use a web form?

No, Yes (in a CM), only when it offers me CM.

So on balance I prefer the old way so that I have CM.

  

How is the choice enforced? 
  
  It's not. I just need to see a plan either in the required XML
  format, or in the database. In the end, it's just a URL either
  way.
  

If there are two separate copies which is seen by the user? 
  
  No. If you provide an XML file, then we'll render it the
  old-fashioned way from a link that we'll put on the review record.
  Maybe I should include an optional field on the release record to
  hold the link.

Please add that link.

    Regards

        Ed Willink
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Wayne Beaton 

  
  

On 03/15/2013 02:08 PM, Ed Willink
  wrote:

Hi
  Wayne
  
  On 15/03/2013 18:01, Wayne Beaton wrote:
  
  
What happens if I edit in the PMI, then
  my colleague edits the XML?
  

Then you will have two separate copies.The PMI stores the plan
information in a database. Drupal provides some revision control
that can be leveraged here.


When I did the import of the existing information, I pulled in
project plans where I could find them. It was a one-way process.


You must choose to either continue to run with an XML file, or
you can use the form elements in the PMI. There is no plan to
attempt to coordinate these.

  
  How do I make that choice?
  

Do you like editing XML and doing revision control in Git, or do you
prefer to use a web form?

  
  How is the choice enforced?
  

It's not. I just need to see a plan either in the required XML
format, or in the database. In the end, it's just a URL either way.

  
  If there are two separate copies which is seen by the user?
  

No. If you provide an XML file, then we'll render it the
old-fashioned way from a link that we'll put on the review record.
Maybe I should include an optional field on the release record to
hold the link.

If you use the PMI, it'll show up there.

  
  If I choose XML, how is the PMI refreshed?
  

It's not.

  
      Regards
  
  
      Ed Willink
  
  ___
  
  cross-project-issues-dev mailing list
  
  cross-project-issues-dev@eclipse.org
  
  https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
  
  


-- 
  Wayne Beaton
  Director of Open Source Projects, The Eclipse Foundation
  Learn about Eclipse
Projects
  
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Ed Willink 

Hi Wayne
On 15/03/2013 18:01, Wayne Beaton wrote:

What happens if I edit in the PMI, then my colleague edits the XML?
Then you will have two separate copies.The PMI stores the plan 
information in a database. Drupal provides some revision control that 
can be leveraged here.


When I did the import of the existing information, I pulled in project 
plans where I could find them. It was a one-way process.


You must choose to either continue to run with an XML file, or you can 
use the form elements in the PMI. There is no plan to attempt to 
coordinate these.

How do I make that choice?

How is the choice enforced?

If there are two separate copies which is seen by the user?

If I choose XML, how is the PMI refreshed?

Regards

Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Wayne Beaton 

  
  

On 03/15/2013 01:51 PM, Ed Willink
  wrote:


  
  Hi Wayne
  
  Once you find your way round, the new PMI provides a better way
  for what it does, but I'm very confused.
  
  For instance, once Luna is out, how will it be possible to access
  the project description for Kepler? Is there a hidden GIT?

No. The project description is the project description. The PMI does
capture revisions (using Drupal's support for this), but I have no
intention of leveraging this for the simultaneous releases page.

The description I mentioned is the description of the release. This
is part of the release record.
 
  On 15/03/2013 17:28, Wayne Beaton
wrote:
  
  

You can also include your plan information directly on the
release record and start assembling your review information
there as well. There is no specific requirement to do this. You
can continue to do what you've been doing all along if you'd
prefer.
  
  Currently my project plan is in Eclipse.org GIT
  mdt\ocl\project-info\plan_kepler.xml which I can understand.
  
  The PMI has some new location that I do not understand.
  
  Are you doing some magical timestamp comparison to detect which of
  the old/new way is in use?

No.
 
  What happens if I edit in the PMI, then my colleague edits the
  XML?

Then you will have two separate copies.The PMI stores the plan
information in a database. Drupal provides some revision control
that can be leveraged here.

When I did the import of the existing information, I pulled in
project plans where I could find them. It was a one-way process. 

You must choose to either continue to run with an XML file, or you
can use the form elements in the PMI. There is no plan to attempt to
coordinate these.
 
  Are you automatically updating the XML and performing GIT commits
  on my behalf?

Nope.
 
      Regards
  
          Ed Willink
  
  
  
  ___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
  Wayne Beaton
  Director of Open Source Projects, The Eclipse Foundation
  Learn about Eclipse
Projects
  
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Wayne Beaton 

  
  
Right... the offset.

Let me know if the offset is incorrect (and the corresponding
correct value).

FWIW, for now, I am the only one who can change any of these values.
I'm thinking that I'll make it so that Planning Council members can
make updates at some point in the future.

Wayne

On 03/15/2013 01:28 PM, Wayne Beaton
  wrote:


  
  Hey Folks.
  
  Can you please take a look at the Kepler page [1] to make sure
  that the entry for your project is correct.
  
  For starters... is your project listed at all? Should it be
  removed?
  
  Please confirm the version number. If there is no version number,
  please let me know what version you'll be including in Kepler.
  
  Note that you'll need to have a corresponding release record for
  the version that you're including in Kepler. You can create a
  version using the PMI. Any project committer can log into their
  project page (e.g. ) click on 'Releases' on the left, and then
  enter information about the release. If you're having trouble with
  this, please let me know.
  
  Ideally, you can enter information about the release. Minimally,
  it would handy if you can provide a description. This will help me
  to disseminate information about your project on your behalf. Note
  that it is best that you keep this information concise. If you
  feel a need to provide a lengthy description, consider using the
  "summary" support to start with a short (e.g. one paragraph)
  summary with a more lengthy description.
  
  You'll notice that a message indicating that the release is
  included in Kepler will automagically appear on the release record
  page (the project page as well).
  
  Note that you do not necessarily need to have a release on the
  exact date of Kepler. If it makes more sense, then you can provide
  a release that occurs on any date leading up to the Kepler release
  date. The bits from whatever release you specify *must* be the
  bits included in the Kepler repository.
  
  You can also include your plan information directly on the release
  record and start assembling your review information there as well.
  There is no specific requirement to do this. You can continue to
  do what you've been doing all along if you'd prefer.
  
  Note that all projects are required to have a project plan.
  
  I am assembling information regarding the use of the PMI in the
  wiki [3]. Watch that page for updates.
  
  Wayne
  
  [1] https://projects.eclipse.org/releases/kepler
  [2] https://projects.eclipse.org/projects/modeling.amp
  [3]
  http://wiki.eclipse.org/Project_Management_Infrastructure/Project_Metadata
  -- 
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
Learn about Eclipse Projects



-- 
  Wayne Beaton
  Director of Open Source Projects, The Eclipse Foundation
  Learn about Eclipse
Projects
  
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Ed Willink 

  
  
Hi Wayne

Once you find your way round, the new PMI provides a better way for
what it does, but I'm very confused.

For instance, once Luna is out, how will it be possible to access
the project description for Kepler? Is there a hidden GIT?

On 15/03/2013 17:28, Wayne Beaton
  wrote:


  
  You can also include your plan information directly on the release
  record and start assembling your review information there as well.
  There is no specific requirement to do this. You can continue to
  do what you've been doing all along if you'd prefer.

Currently my project plan is in Eclipse.org GIT
mdt\ocl\project-info\plan_kepler.xml which I can understand.

The PMI has some new location that I do not understand.

Are you doing some magical timestamp comparison to detect which of
the old/new way is in use?

What happens if I edit in the PMI, then my colleague edits the XML?

Are you automatically updating the XML and performing GIT commits on
my behalf?

    Regards

        Ed Willink
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Capture Kepler participation information

2013-03-15 Thread Wayne Beaton 

  
  
Hey Folks.

Can you please take a look at the Kepler page [1] to make sure that
the entry for your project is correct.

For starters... is your project listed at all? Should it be removed?

Please confirm the version number. If there is no version number,
please let me know what version you'll be including in Kepler.

Note that you'll need to have a corresponding release record for the
version that you're including in Kepler. You can create a version
using the PMI. Any project committer can log into their project page
(e.g. ) click on 'Releases' on the left, and then enter information
about the release. If you're having trouble with this, please let me
know.

Ideally, you can enter information about the release. Minimally, it
would handy if you can provide a description. This will help me to
disseminate information about your project on your behalf. Note that
it is best that you keep this information concise. If you feel a
need to provide a lengthy description, consider using the "summary"
support to start with a short (e.g. one paragraph) summary with a
more lengthy description.

You'll notice that a message indicating that the release is included
in Kepler will automagically appear on the release record page (the
project page as well).

Note that you do not necessarily need to have a release on the exact
date of Kepler. If it makes more sense, then you can provide a
release that occurs on any date leading up to the Kepler release
date. The bits from whatever release you specify *must* be the bits
included in the Kepler repository.

You can also include your plan information directly on the release
record and start assembling your review information there as well.
There is no specific requirement to do this. You can continue to do
what you've been doing all along if you'd prefer.

Note that all projects are required to have a project plan.

I am assembling information regarding the use of the PMI in the wiki
[3]. Watch that page for updates.

Wayne

[1] https://projects.eclipse.org/releases/kepler
[2] https://projects.eclipse.org/projects/modeling.amp
[3]
http://wiki.eclipse.org/Project_Management_Infrastructure/Project_Metadata
-- 
  Wayne Beaton
  Director of Open Source Projects, The Eclipse Foundation
  Learn about Eclipse
Projects
  
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev