User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
Hi Wayne,
That works for me. Also, this would let us 'keep the brand'
better.
Is there a plan for the domain locationtech.org? Apologies if I
missed it in the list of bugs.
Cheers,
Jim
On 11/25/19 12:39 PM, Wayne Beaton
wrote:
Hi Jim.
Sorry for the delay.
We agree with your reasoning. Let's do one better and just
leave the project names as "LocationTech *". Does that work
for you?
Wayne
On Tue, Nov 19, 2019 at 2:54
PM Jim Hughes <jhughes@xxxxxxxx> wrote:
Hi Wayne,
Is it possible to keep the LocationTech brand around?
I absolutely want to see the projects be able to keep the
org.locationtech.* package names and groupIds. Doing that
for the projects once they are rebranded from LocationTech
to Eclipse will be a little awkward...
As a way to split the difference, could we rebadge the
projects as "Eclipse LocationTech" <projectName>?
Cheers,
Jim
On 11/19/19 2:28 PM, Wayne Beaton wrote:
In part, we're merging the LocationTech
forge into the Eclipse Forge because the LocationTech
working group (which the forge was originally created to
support) no longer exists. There is also the practical
matter that the main forge has developed faster than
we've been able to maintain the LocationTech forge and
that the project teams will get better service by
leveraging the main forge.
Technical namespaces do not need to be changed.
Projects can continue to use org.locationtech.*
If you have concerns about specific aspects of what
we're doing, please raise them on the bug reports (the
team that supports our infrastructure, for example,
doesn't monitor this list). For issues regarding repo.locationtech.org,
weigh in on Bug 528040.
I believe this is just combining
infrastructure to reduce costs.
I am kind of curious about repo.locationtech.org
--> repo.eclipse.org
as we had defined some specific workflows around
the use of classifiers to mark jars that had been
modified for eclipse release (often a subset of
the maven central jar with some IP removed).
Thank you Wayne for this reminder
and details about issues to track.
Sorry in case I've missed it, can you tell
us something about the story behind? The
question I'm having in my mind: Is it not
allowed to use locationtech.org
in sourcecode anymore?
The Eclipse Foundation Webmaster and
Project Teams have set December 2/2019 as
the date to complete merging the
LocationTech Forge into the Eclipse Forge.
We're tracking this work on Bug
528037.
For most committers, this should not be
disruptive. The existing source code
repositories on GitHub will not be
impacted.
Take note, however, that the mailing
lists will be moved from @locationtech.org
to @eclipse.org.
As part of this, the technology-pmc@xxxxxxxxxxxxxxxx
mailing list will be changed to locationtech-pmc@xxxxxxxxxxx
to avoid conflicting with the existing
mailing list for the Eclipse Technology
PMC. The webmaster plans to preserve
mailing list archives and move all
subscribers to the new list. Please plan
to update your contacts. We're tracking
this with Bug
549639.
The other piece that will impact some
of you is the migration of repo.locationtech.org.
Please use Bug
528040 to provide input into this
process and otherwise monitor progress.
Note that the open source projects will
all be rebranded from "LocationTech *" to
"Eclipse *" (see Bug
553103).
There are some other activities (all
described in "blocker"s on Bug
528037) that you can use to provide
input and feedback, and otherwise monitor
progress.
Thanks,
Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.