3 ms·

> follow the proper release procedures for it What happens when your thing or nothing close to your thing will ever see the light of day?

• no-name-here 4mo ago
  1. If google said ok but don't release under google’s name/in google’s repo, do that. 2. If google said no this goes against our goals for the product, don't release it if you want to keep working for google?
  • whstl 4mo ago
    It was clearly greenlighted by management. The person who made the announcement was Addy Osmani, who was manager of the fired developer at the time. This is in a Google-owned organization, with several other similar repositories, a lot of them using the same API.
    • burakemir 4mo ago
      Looks like Addy Osmani is leaving, too.
• sib 4mo ago
  Is that relevant here, given that Google was creating an official thing quite close to his thing at the same time? (And why are we writing like this?)
  • DANmode 4mo ago
    > Google was creating an official thing quite close to his thing Just link to it.
    • Arainach 4mo ago
      It's mentioned in the original link for this post.
  • seanhunter 4mo ago
    Fair to point out, the official google thing, was quite a lot worse than his thing. (I’m quite into the whole “Posting in free verse” idea)
  • gedy 4mo ago
    Would you like them in a house? Would you like them with a mouse?
    • kazinator 4mo ago
      AI am Sam ... Sam AI am ... My program made green eggs and ham ...
      • DANmode 4mo ago
        Is there a smell of toast burning where you are?
• Arainach 4mo ago
  None of that is relevant. You're working on things for their employer, they control when and if anything is released. Most of us have worked on projects that were cancelled - even when that happens you don't just release it anyway.
  • DANmode 4mo ago
    > they control when and if anything is released I don’t think that’s how APIs work at all. Upon reflection, the only thing this guy did wrong was put his name on the thing…