News for hackers. Stuff that matters.
Re:GitLab 8.10 Released with Wildcard Branch Protection and ... by aw3c2 on Friday July 22, 2016 @05:53PM (#12147037)
Now please tone down the incredible amount of unwanted mail you send to new signups, got my colleagues fairly puzzled after I insisted we use GitLab instead of GitHub. :(
Re:GitLab 8.10 Released with Wildcard Branch Protection and ... by plusECON on Saturday July 23, 2016 @01:41PM (#12150256)
GitLab marketer here - sorry if we inundated your team! This section of our handbook has info on emails, but it's due for an update from me: https://about.gitlab.com/handbook/marketing/demand-generatio...

A typical frequency would be 2-5 emails over the first 7 days after signup, then ~2/month afterward (unless you also sign up for security updates). I'd like to make a change so that it's 2-5 emails over the first 9 days after signup. About 80% of people only qualify for newsletters and one onboarding or confirmation email in the first week after signup, whereas people at companies we suspect more interested in EE and/or support will receive 1-3 extra from our business development reps. We try to limit our more "salesy" outreach with "lead scoring", an industry standard for IDing those most likely interested in those type of emails (see https://about.gitlab.com/handbook/marketing/demand-generatio... ).

The response to our emails is usually positive (sometimes even apologetic to the BDRs for slow response) as the BDR team can attest to, though we do get our fair share of unsubscribes (our reps include a one-click unsub link in their signature - highly unusual!) and the occasional two-word "f* you!" replies. Let me add that we don't ask for phone numbers from new signups and you will not be burdened with nonsense voicemails from us!

That being said, feedback like this is always a good catalyst to reevaluate and look for opportunities to adjust and improve. As stated in the first link I provided, "What [you] receive depends on how [you] came to find us and what we believe will be most helpful to [you]", so any specific feedback on how to be more helpful is greatly appreciated! -Hank Taylor

Re:GitLab 8.10 Released with Wildcard Branch Protection and ... by mrmondo on Friday July 22, 2016 @07:36PM (#12147550)
That's a rather rude, unconstructive way of asking for someone to do something for free for you. How about logging a bug, or if you have - linking to it here to get some additional traction?
Re:GitLab 8.10 Released with Wildcard Branch Protection and ... by aw3c2 on Saturday July 23, 2016 @05:41AM (#12148951)
Can you tell me where to log that bug?
Re:GitLab 8.10 Released with Wildcard Branch Protection and ... by mrmondo on Sunday July 24, 2016 @03:05AM (#12152557)
The first result on google for 'log gitlab bug': https://gitlab.com/gitlab-org/gitlab-ce/issues

Don't worry about the 'ce vs ee' thing, it makes no difference, it's all the same code and regardless, the company and the community care about the product and will respond.

Re:GitLab 8.10 Released with Wildcard Branch Protection and ... by swsieber on Saturday July 23, 2016 @09:44AM (#12149432)
The second yahoo result for "gitlab issue tracker", (the first was the about page): https://gitlab.com/gitlab-org/gitlab-ce/issues

For the record, it's pretty easy to change your notification settings.

Re:GitLab 8.10 Released with Wildcard Branch Protection and ... by aw3c2 on Saturday July 23, 2016 @01:13PM (#12150141)
That's self-hosted GitLab CE, I meant mails from when people sign up at gitlab.com