FYI,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=458974
I like to start from ideal and work back to realistic.
Realistically, we don't have a proper product manager at this point in
time, and we don't have extra engineering cycles. Extracting data from
what we already have and prescribing p
On 02/02/2015 06:19 PM, Doug Schaefer wrote:
From: Lars Vogel mailto:lars.vo...@vogella.com>>
> Ideally, we have a product/project manager who puts all this together.
Don’t let engineers do your marketing :).
-1, having worked for a large software company in the past, I
think the
Hi
On 02/02/2015 17:18, Mickael Istria wrote:
On 02/02/2015 06:07 PM, Lars Vogel wrote:
> Ideally, we have a product/project manager who puts all this
together. Don’t let engineers do your marketing :).
-1, having worked for a large software company in the past, I think
the current platform
From: Lars Vogel mailto:lars.vo...@vogella.com>>
> Ideally, we have a product/project manager who puts all this together. Don’t
> let engineers do your marketing :).
-1, having worked for a large software company in the past, I think the current
platform approach of having the developer describ
On 02/02/2015 06:07 PM, Lars Vogel wrote:
> Ideally, we have a product/project manager who puts all this
together. Don’t let engineers do your marketing :).
-1, having worked for a large software company in the past, I think
the current platform approach of having the developer describe his
d
> Ideally, we have a product/project manager who puts all this together.
Don’t let engineers do your marketing :).
-1, having worked for a large software company in the past, I think the
current platform approach of having the developer describe his development
is much more efficient.
On Mon, Feb
Ideally, we have a product/project manager who puts all this together. Don’t
let engineers do your marketing :).
D
From: Wayne Beaton mailto:wa...@eclipse.org>>
Organization: The Eclipse Foundation
Reply-To: Cross project issues
mailto:cross-project-issues-dev@eclipse.org>>
Date: Monday, Februa
Okay. Avoidance of more work is a requirement. Forget all that silliness
about a common XML file format and putting extra files in features.
Wayne
On 02/02/15 10:03 AM, Daniel Megert wrote:
For us it would mean more work, which I'd like to avoid. Having one
document easily allows to tools to e
For us it would mean more work, which I'd like to avoid. Having one
document easily allows to tools to e.g. check for XHTML validity, and help
fix such issues. If the document is generated out of pieces, then it can
be a tedious task to get to a generated document that is valid. The
extension p
I share your concerns.
The need to find and fix typos doesn't change. We can use some sort of
weighting to encourage ordering. Grouping can be done by feature.
I'm more concerned about the generation of a massive all-features-ever
listing than I am about the N&N for any particular release.
Our N&N is compiled by the input of each committer (sub-project) directly
into our news repo (
http://git.eclipse.org/c/www.eclipse.org/eclipse/news.git) or via Gerrit
for contributors. Before we publish the milestone, someone from the team
edits the document to bring it into a good and readable
> I only ever see the Platform/JDT N&N in web page form. How is this web
page constructed? Is it just done by hand, or is it somehow automatically
generated from some data source?
We write it by hand as HTML.
On Mon, Feb 2, 2015 at 3:25 PM, Wayne Beaton wrote:
> I agree with Dani. Each projec
I agree with Dani. Each project's N&N should be project-specific.
I only ever see the Platform/JDT N&N in web page form. How is this web
page constructed? Is it just done by hand, or is it somehow
automatically generated from some data source?
The ideal, I think, would be to have a common for
Hi
A mishmash is certainly undesirable, but they are indirected and maybe a
style consensus might materialize. (Maybe the PMI might even help format
it).
If the PMI doesn't help, we have to introduce a new all-projects
database/HTML file.
Regards
Ed Willink
On 02/02/2015 14:1
The PMI has a single field that you can use to record a link. IMHO, a
mishmash of links with N&N in different formats isn't very useful.
Wayne
On 02/02/15 05:30 AM, Ed Willink wrote:
Hi
I think the PMI has/can have a full list of all the N&Ns, so is it
possible for the PMI to create an N&N i
Greetings.
No complains yet. Good. However, there’s a difference between _thinking_ that
something is a good(not bad) idea and actually _implementing_ it. Thus, before
we start asking for modifications in PMI or settings up other solutions, I’d
like to know who would be interested to participa
> I think the correct solution would be to extend the purpose of the
Platform N&N to include newsitems from the EPP side.
No, that is not the correct solution. The EPP/main download side can have
and advertise a joint N&N.
Dani
From: Lars Vogel
To: Cross project issues
Date: 02.02
Hi
I think the PMI has/can have a full list of all the N&Ns, so is it
possible for the PMI to create an N&N index similar to the Help
Documentation index so that the Platform N&N links to the overall N&N
index? Impact one line per project in an index.
If we want a 'three item' overview, perh
Sounds interesting...
Right now we are maintaining a list of N&N links for every package, but (a)
these are not very popular... and (b) they are most of the time out of date
because I tend to review these for the release only, i.e. I don't have the
time to update them regularly for every milestone
Hi Marcel,
I think the correct solution would be to extend the purpose of the Platform
N&N to include newsitems from the EPP side.
Best regards, Lars
On Mon, Feb 2, 2015 at 11:11 AM, Marcel Bruch
wrote:
> Greetings cross-projects,
>
> I’d like to get your thoughts about a joint N&N page for Ma
Greetings cross-projects,
I’d like to get your thoughts about a joint N&N page for Mars Milestones.
The platform maintains a N&N page [1] for changes on the Platform/JDT/PDE. All
press releases, blogs and tweets about new milestones are pointing to this page
and as such it is the most prominent
21 matches
Mail list logo
