Stories
Slash Boxes
Comments

SoylentNews is people

Submission Preview

Link to Story

GitHub to devs: 'We ignored you but we never stopped caring'

Accepted submission by Arthur T. Knackerbracket at 2016-02-16 02:55:01
Code

Story automatically generated by StoryBot Version 0.0.1f (Development).

Note: This is the complete story and will need further editing. It may also be covered
by Copyright and thus should be acknowledged and quoted rather than printed in its entirety.

FeedSource: [TheRegister] collected from rss-bot logs

Time: 2016-02-15 02:05:09 UTC

Original URL: http://www.theregister.co.uk/2016/02/15/github_sourceforge_both_say_sorry_to_aggrieved_users/ [theregister.co.uk]

Title: GitHub to devs: 'We ignored you but we never stopped caring'

Suggested Topics by Probability (Experimental) : 18.2 science 18.2 hardware 18.2 code 18.2 business 18.2 OS 9.1 careers

--- --- --- --- --- --- --- Entire Story Below --- --- --- --- --- --- ---
 
 

GitHub to devs: 'We ignored you but we never stopped caring'

GitHub has promised to pay better attention to the concerns of users.

                               

In January, more than 1,100 project maintainers complained [theregister.co.uk] the popular code-host was ignoring them.

                               

Now, GitHub's Brandon Keepers has taken the first tentative step to try and soothe the seething masses [github.com].

                               

Here's his letter in full:

                               

We hear you and we're sorry. We've been slow to respond to your letter and slow to respond to your frustrations.

We're working hard to fix this. Over the next few weeks we'll begin releasing a number of improvements to Issues, many of which will address the specific concerns raised in the letter. But we're not going to stop there. We'll continue to focus on Issues moving forward by adding new features, responding to feedback, and iterating on the core experience. We've also got a few surprises in store.

Issues haven't gotten much attention from GitHub these past few years and that was a mistake, but we've never stopped thinking about or caring about you and your communities. However, we know we haven't communicated that. So in addition to improving Issues, we're also going to kick off a few initiatives that will help give you more insight into what's on our radar. We want to make sharing feedback with GitHub less of a black box experience and we want to hear your ideas and concerns regularly.

We'll be in touch next week. Sorry it's taken so long, and thank you for everything.

—GitHub

The behaviour of Issues on GitHub was the first item on the insurrectionists' list.

                               

GitHub's woes were compounded by outages in late January after a power outage in its main data centre, which required a red-faced mea culpa [theregister.co.uk].

                               

In other dev news, the new owners of SourceForge have attracted applause for killing off its hated DevShare program, announcing [sourceforge.net]: “As of last week, the DevShare program was completely eliminated”.

                               

DevShare was a revenue-sharing bundling program that led to embarrassment [theregister.co.uk] last June, when advertisements were wrapped around the famous open source image-wrangling program The GIMP.

                               

That led other open source maintainers to look elsewhere to host their files – including GitHub.

                               

SourceForge Media president Logan Abbott writes that the platform wants to “restore our reputation as a trusted home for open source software, and this was a clear first step towards that”.

                               

Abbott also says SourceForge and Slashdot will soon get full HTTPS support, and the company will focus on “building out our site features and establishing community trust”. ®

                               


                                        Sponsored:
                                        Go beyond APM with real-time IT operations analytics [theregister.com]
                               

                       


Original Submission