-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'd like to take over the Seattle chapter of Perl Mongers #156
Comments
Hey @chardin you can fork the repo in github and post a pull request against upstream (this repo). Or just post your diff and I'll apply it for you. Thanks! |
I guess I was unclear before.
I checked out the git repo, created a topic branch for this change, and tried to push that topic branch to the repo. This is how I have forked repos before, and created branches against which I can make pull requests to master. Pushing my topic branch failed with the error I mentioned.
Is there some other way to implement your suggestion, and if so, what is it?
I'll want to be able to do this in future, so I'd like to get this working.
I have some other questions as well. There's an existing mailing list for SPUG, and I'd like to be able to use it to contact the members. Is that hosted by Perl Mongers, and if so, what do I need to do to administer it?
I'm guessing that there's no way for me to get seattleperl.org, since Perl Mongers doesn't host PM chapter websites any more.
… On Oct 21, 2020, at 10:26 AM, Jay Hannah ***@***.***> wrote:
Hey @chardin <https://github.com/chardin> you can fork the repo in github and post a pull request against upstream (this repo). Or just post your diff and I'll apply it for you. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#156 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIE3WFGQDADXOMMS2GBVADSL4KV7ANCNFSM4SXKZCFA>.
|
Hi @chardin, I think what you did was We host this mailing list, yes: https://mail.pm.org/mailman/listinfo/spug-list You'll become the admin of that once I have your full name / email address etc from your PR. We have no control over seattleperl.org, no. |
Thank you, that is quite clear! I have created a pull request at chardin#1 for your review. |
Is there something wrong with my pull request? It's been over a week and it appears to be unmerged. Is there something else I need to do? |
@chardin nope, sorry, my hobby laptop died. Rigging my work laptop up for also doing my hobby github stuff. |
|
I think I gave a link to the webpage I want to use. It was in the XML, and https://www.pm.org/groups/95.html seems to have a pointer to it. Or do you want something else? Everything else seems to be working. I did change the password. |
Ah, gotcha cool. 👍 |
It is date stamped. And I won't need a year to do the right thing.
Thank you very much!
… On Nov 6, 2020, at 9:59 AM, Jay Hannah ***@***.***> wrote:
Ah, gotcha cool. 👍
Can you please put a date stamp on https://www.naming-schemes.org/seattle.pm/ <https://www.naming-schemes.org/seattle.pm/> ? If the website is still blank in a year I'll deactivate your group. ( We don't want a bunch of zombie groups in our active group list. :) ) Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#156 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIE3WGT2TILOIQEF52HSWDSOQ2P7ANCNFSM4SXKZCFA>.
|
lol thanks! |
Hi, I'm Chuck Hardin. I used to run Thousand Oaks Perl Mongers, and have given talks at Boston, LA, and Orange County Perl Mongers. I've moved to Redmond now, and I'd like to keep promoting Perl here.
I tried to contact Andrew Sweger, the current Tsar of record for Seattle Perl Mongers, but the email bounced. I did a quick search, and was saddened to see that he died in 2019.
I'd like to take over the group. I tried to generate a pull request on a fork of perl-mongers.xml, as suggested in the relevant FAQ, but got an error:
remote: Permission to perlorg/www.pm.org.git denied to chardin
I'm not sure how to proceed. How do we do this?
The text was updated successfully, but these errors were encountered: