googlecode transition: let's get this moving

[Amelia A Lewis]

Hey, gang,

This mail has two parts:

1) I'm reminding you of issue 160: we need to transition away from
googlecode, because it's going read-only on the first of August, and
will be phased out after. We have about two weeks, at this point (there
have been other priorities).

2) Original suggestion was to move to github, with a project
unaffiliated with TIBCO Software Inc., the employer of all the
committers. This was primarily to provide some distance, for optics,
whatever you'd like to call it. Independence? Eric made the suggestion
that the project move under the umbrella of TIBCO's open-source efforts
at github.

This is the URL provided by Googlecode for tools supporting an export
to (presumably independent?) github:
https://code.google.com/p/support-tools/wiki/MigratingToGitHub

Eric, if you have a URL indicating how this works for exporting to
tibco-umbrella github, could you provide a link? Or if it's the same
process, just different credentialing or something, a brief summary?

So, a call for vote:

[ ] independent github
[ ] tibco-umbrella github
[ ] other option: ____________ [please indicate suggested alternative,
in other words]

Committers, please respond. Contributors, if you care to, please
respond. We'll let this run for three days, so 1PM EDT Friday, which
means basically that we'll implement whatever decision has been agreed
to starting next week.

In addition, please raise any concerns you have. Mine: we need
preservation of histories and materials, insofar as that is possible;
we've nomaded about enough that we don't want to lose that information
yet again.

For information: we *can* potentially host independent (probably svn?)
and some issue-tracking software on genxdm.org. That host happens to
need a hardware upgrade, but that's all in queue, awaiting a
sufficiency of round two-its to be delivered (it's a virtual host on a
machine scheduled for upgrade).

Amy!
--
aal, et alia, et alii

[Eric Johnson]

Thanks for getting this started, Amy.

One minor point, which you didn't raise, which would make this migration more complicated, but we should consider at least long enough to discard it. Do we want one Git repository for all the GenXDM code, or do we want more than one?

On Tue, Jul 14, 2015 at 10:18 AM, Amelia A Lewis <aal...@gmail.com> wrote:

Hey, gang,

This mail has two parts:

1) I'm reminding you of issue 160: we need to transition away from
googlecode, because it's going read-only on the first of August, and
will be phased out after. We have about two weeks, at this point (there
have been other priorities).

2) Original suggestion was to move to github, with a project
unaffiliated with TIBCO Software Inc., the employer of all the
committers. This was primarily to provide some distance, for optics,
whatever you'd like to call it. Independence? Eric made the suggestion
that the project move under the umbrella of TIBCO's open-source efforts
at github.

This is the URL provided by Googlecode for tools supporting an export
to (presumably independent?) github:
https://code.google.com/p/support-tools/wiki/MigratingToGitHub

Eric, if you have a URL indicating how this works for exporting to
tibco-umbrella github, could you provide a link? Or if it's the same
process, just different credentialing or something, a brief summary?

Absolutely the same process. The repository will just have a URL associated with TIBCO, rather than one associated with one of our individual accounts.

 

So, a call for vote:

[ ] independent github
[ ] tibco-umbrella github 

TIBCO umbrella Github.

 

[ ] other option: ____________ [please indicate suggested alternative,
in other words]

Committers, please respond. Contributors, if you care to, please
respond. We'll let this run for three days, so 1PM EDT Friday, which
means basically that we'll implement whatever decision has been agreed
to starting next week.

In addition, please raise any concerns you have. Mine: we need
preservation of histories and materials, insofar as that is possible;
we've nomaded about enough that we don't want to lose that information
yet again.

Migrating the source shouldn't be a challenge. Let me know if you have trouble figuring out the Subversion to Git migration process.

https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git

Based on discussions I've had with others, the most annoying part is mapping user names.

 

For information: we *can* potentially host independent (probably svn?)
and some issue-tracking software on genxdm.org. That host happens to
need a hardware upgrade, but that's all in queue, awaiting a
sufficiency of round two-its to be delivered (it's a virtual host on a
machine scheduled for upgrade).

Not worth your time. Github is available now, and has all the tooling we need (well, except for the generated site on genxdm.org).

 

Amy!

--
aal, et alia, et alii

--
You received this message because you are subscribed to the Google Groups "GenXDM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to genxdm+un...@googlegroups.com.
To post to this group, send email to gen...@googlegroups.com.
Visit this group at http://groups.google.com/group/genxdm.
For more options, visit https://groups.google.com/d/optout.

[Amelia A Lewis]

From my perspective, I'd say one repo. The design of the build system
expects a hierarchy of projects (a flat hierarchy, but a hierarchy
nonetheless). All of the child projects depend upon the parent, which
shares information on how to perform the build with all its children.
This makes updating those bits simpler and more consistent (a known
issue with external projects based on GenXDM and using copied bits of
the build system; they are forced to update independently and
inevitably fall a bit out of sync).

But if someone feels strongly otherwise, I'd be interested in the
argument in favor of separate repos.

Amy!

[Eric Johnson]

I'm convinced. Wasn't really arguing for separate repos. Just wanted to make sure we had a discussion, in case someone is lurking out there with better ideas.

Eric.

[Amelia A Lewis]

A reminder to committers: please do vote on the section marked "a call
for vote". Contributors, if you're so inclined, please vote as well.

Amy!
----- Begin forwarded message -----
From: Amelia A Lewis <aal...@gmail.com>
Date: Tue, 14 Jul 2015 13:18:19 -0400
To: GenXDM Mailing List <gen...@googlegroups.com>
Subject: googlecode transition: let's get this moving

Hey, gang,

This mail has two parts:

1) I'm reminding you of issue 160: we need to transition away from
googlecode, because it's going read-only on the first of August, and
will be phased out after. We have about two weeks, at this point (there
have been other priorities).

2) Original suggestion was to move to github, with a project
unaffiliated with TIBCO Software Inc., the employer of all the
committers. This was primarily to provide some distance, for optics,
whatever you'd like to call it. Independence? Eric made the suggestion
that the project move under the umbrella of TIBCO's open-source efforts
at github.

This is the URL provided by Googlecode for tools supporting an export
to (presumably independent?) github:
https://code.google.com/p/support-tools/wiki/MigratingToGitHub

Eric, if you have a URL indicating how this works for exporting to
tibco-umbrella github, could you provide a link? Or if it's the same
process, just different credentialing or something, a brief summary?

So, a call for vote:

[ ] independent github
[ ] tibco-umbrella github

[ ] other option: ____________ [please indicate suggested alternative,
in other words]

Committers, please respond. Contributors, if you care to, please
respond. We'll let this run for three days, so 1PM EDT Friday, which
means basically that we'll implement whatever decision has been agreed
to starting next week.

In addition, please raise any concerns you have. Mine: we need
preservation of histories and materials, insofar as that is possible;
we've nomaded about enough that we don't want to lose that information
yet again.

For information: we *can* potentially host independent (probably svn?)
and some issue-tracking software on genxdm.org. That host happens to
need a hardware upgrade, but that's all in queue, awaiting a
sufficiency of round two-its to be delivered (it's a virtual host on a
machine scheduled for upgrade).