-gobblin-users, -user

Few questions:

* What is the "Migration of Travis CI to use the Apache infrastructure"
going to entail? I'm guessing builds will happen on Apache Jenkins
instances, how about pre-commit checks? Is there a plan to add pre-commit
checks, using tools such as YETUS?
* I think there is a way in Github to completely remove the Issues section,
other projects (such as Spark) have done this
* Maybe good to follow Sparks format for opening PRs - title of each PR
contains the JIRA and component, and each PR has a section summarizing what
was changed and how it was tested

--Sahil

On Wed, Jul 19, 2017 at 3:14 PM, Abhishek Tiwari <
[email protected]> wrote:

> Hey all,
>
> As part of the Gobblin project's recent move to Apache, we are migrating
> the mailing lists to Apache infrastructure as well, so that *the existing
> Google groups will become read-only* at some point in the near future.
>
> To keep receiving updates about Gobblin or to participate in development
> discussions, please *subscribe* to the following lists:
>
> [email protected] -- for usage questions, help and
> announcements. [Subscribe <[email protected]>] [
> Archives
> <http://mail-archives.apache.org/mod_mbox/incubator-gobblin-user/>]
> [email protected] -- for people who want to contribute
> code to Gobblin. [Subscribe <[email protected]>]
> [Archives
> <http://mail-archives.apache.org/mod_mbox/incubator-gobblin-dev/>]
> [email protected] -- for people who want to contribute
> code to Gobblin. [Subscribe
> <[email protected]>] [Archives
> <http://mail-archives.apache.org/mod_mbox/incubator-gobblin-commits/>]
>
> Additionally, the Gobblin Gitter chat rooms: [Gobblin Lobby
> <https://gitter.im/gobblin/Lobby>] [Gobblin Cluster
> <https://gitter.im/gobblin/gobblin-cluster>] is where many Gobblin
> developers and users hang out to answer questions and chat.
>
> *The other infrastructure and process changes with Apache migration are: *
>
> 1) Migration of linkedin/gobblin code base to Apache's Git repository. [In
> Progress]
> 2) Migration of Google groups mailing list (this list) to Apache mailing
> lists. [In Progress]
> 3) Migration of Travis CI to use the Apache infrastructure. [Scheduled]
> 4) Migration of Wiki to Apache Confluence wiki. [Scheduled]
> 5) Migration of Github Issues to Apache JIRA. [Done]
> 6) Migration of all existing pull requests to the Apache Github mirror
> repository. [Scheduled]
>
> We will track the progress of the above items on Gobblin's Apache mailing
> lists.
>
> *What you should do:*
>
> * Sign up for the Apache user, dev and commits mailing list (as described
> above)
> * Sign up for an Apache JIRA account and open any issues that you care
> about in Apache Gobblin JIRA project (https://issues.apache.org/
> jira/browse/GOBBLIN)
> * Sign up for an Apache Confluence account (https://cwiki.apache.org/
> confluence/display/GOBBLIN)
> * Stop creating GitHub issues immediately. Create new problem reports as
> JIRAs now.
>
> Regards,
> Abhishek
>
> --
> You received this message because you are subscribed to the Google Groups
> "gobblin-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/gobblin-users/CAFjTMnwyPbd1ngGa7JX%3DUKHkPwJ1YhJtA-ZN8xxDZjJbu1v%
> 2BXw%40mail.gmail.com
> <https://groups.google.com/d/msgid/gobblin-users/CAFjTMnwyPbd1ngGa7JX%3DUKHkPwJ1YhJtA-ZN8xxDZjJbu1v%2BXw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Sahil Takiar
Software Engineer at Cloudera
[email protected] | (510) 673-0309

Reply via email to