Agreed. We should release in this state.
Agreed that 2.0.4 is a better version number.
I think we agree that all are great. To save designer work (and a bit of money), why not use them all? They have a similar color scheme, but some are warmer, others are colder. So maybe C for March, B for June, D for September and A for December? I think it would work if your reference is the northern hemisphere at least.
Yes, I'm not getting the same error, but I can see that there is a problem with the target platform. The artefact com.swabunga:jazzy:jar:1.0.0 can no longer be found in Maven Central. Some work is required to remedy this.
I think the best option would be to keep eclipse.org/<project>
forever. There is just too much history for this to be thrown over board. The organisation can move to eclipse-foundation.org
, which I think makes more sense. Especially given that employees of the Foundation are already using nn@eclipse-foundation.org
. The redirect from https://eclipse-foundation.org
to https://www.eclipse.org/org/
should be swapped. I think this would be the least disruptive solution.
The eclipse.org domain is for both existing projects and the Foundation. Any change to that is over my pay grade, and would require the membership to provide that direction
As a member of the Board representing the Contributing members, I would like to raise this as a Board issue.
My message to the mailing list:
Yes, I think terminating the project would be premature. It appears it does have active users (I cannot find any usable download stats), and even a few contributors. It just needs active committers, of which there only have been one since the project was moved to Eclipse.
Substantial effort was done to prepare the project for Eclipse. But I have not been able to do much the past few years. I do little programming, and have not prioritized fixing the few issues we have in TeXlipse. Especially because I don’t use it myself.
I think it would be worthwhile attempting to recruit new committers and revive the project.
I agree with Wayne here. Keeping Mylyn as a TLP would just create too much overhead for a small team.
I'm thinking that just merging Mylyn Docs into the new project, and having all of its repositories just accessible to the whole team is the easiest way to go. Please correct me if I'm wrong.
I think that would work just fine. It would be practical to separate WikiText and EPUB into two separate Git repositories. But that is a different story.
I agree. Mylyn Docs is functional and mature. There are some subprojects within Mylyn Docs that are pretty much ready for retirement though. In any case I would like to help out keeping the EPUB code alive.
I can verify that this is still a (minor) issue on a 111ppi screen. I believe when I reported this I was using a 220ppi screen (older macBook Pro). I guess the new high end are the new macBook Pros, which have a density of 250ppi.
Bugzilla Link | 561330 |
Status | NEW |
Importance | P3 normal |
Reported | Mar 21, 2020 17:32 EDT |
Modified | Mar 21, 2020 18:34 EDT |
The Eclipse installer now offers a button where consumers can choose to donate funds to the EPP project they are installing. A similar function should be available at the donation page https://www.eclipse.org/donate/.
Thanks for the script. Mylyn Docs has an ongoing discussion regarding this. See bug 533122.
These are indeed good ideas!
I believe the dedicated server can be taken down. It's been years since it's been useful, for me at least, since most mirrors are now much faster. I'm also one of those who paid $100 for an Eclipse t-shirt a while back. So paying a bit extra for SWAG might work :)
Having Friends choose the name of the train and which splash screen to use could be fun and interesting. We would have to be careful so we don't end up with a "Eclipsy McEclipseFace" situation though.
Getting help from Friends prioritizing FEEP projects may also work. Although it appears the problem here is getting someone to do the implementation.
Bugzilla Link | 507200 |
Status | NEW |
Importance | P3 normal |
Reported | Nov 08, 2016 03:20 EDT |
Modified | Aug 18, 2021 11:42 EDT |
It would be great if it could be made to fit the page so that it's possible to read more of the text. See example at https://wiki.eclipse.org/Science_WG#Calendar.
Bugzilla Link | 494710 |
Status | NEW |
Importance | P3 normal |
Reported | May 27, 2016 03:05 EDT |
Modified | Nov 10, 2020 09:30 EDT |
As the summary says, some of the logos are blurry.
(In reply to Mickael Istria from comment #23)
I've got a dummy question here: since we want this check to happen before
the JVM starts most likely (since it's about finding the right JVM), does
that mean that the dialog must be implement in the native widget technology
(and then repeated 3 times)?
I guess this could be done in more or less shared code
The detection mechanism would be platform specific. On OS X there is a registry that can be queried to produce XML that can be parsed. See https://github.com/turesheim/eclipse-launcher/blob/master/net.resheim.eclipse.launcher.macosx/src/net/resheim/eclipse/launcher/macosx/OSXJavaLocator.java
(In reply to Denis Roy from comment #7)
posts/month to today's 3200 posts/month). We have had some pretty bad
issues with the forums for a long time, the most critical having been fixed
in the last 6 months.
Which is a plausible cause for the decline.
FWIW I completely agree with Stephen in comment #3. We should probably have a split between Q&A and discussion forums.
(In reply to John Arthorne from comment #5)
Do you have metrics available on the current activity level in the forums
and NNTP? I.e., number of questions/replies/views per day. My perception is
that it is declining but there are still a significant number of active
users there. We need to make decisions based on feedback from more than a
handful of people that have been on these bugzilla discussions.
It would be nice to have those numbers, but what could we understand from them? It could be that people are staying away from NNTP because they simply do not know about it (and that it's old-fashioned). And that they are staying away from the HTTP forums because they are not good enough.