Open pwnorbitals opened 4 years ago
:O
first Discord, now Twitter, there are a lot of channels I'm unaware of...
Youtube as well! The twitter account is a bit pointless, but I'll try and keep it updated whenever we have a new news entry, I don't really see any reason to get rid of it.
Well I advocate that having no account is better than an unmaintained one (which could degrade the image of the project) If the intent is to update it, then it’s awesome !
Have a new release ci pipeline push a tweet about it 🙃
bad joke
Have a new release ci pipeline push a tweet about it
New releases defo should be tweeted out.
Yep, I think we need to work on our community outreach. Especially as we're replicating an existing game's server, building excitement and attracting contributors is always going to be a challenge. For the project to have long term success I think getting the word out is as important as the technical implementation
Does anyone know of a bot that can post if there was a new CI build?
What about Github Actions? https://github.com/marketplace/actions/twitter-action
Does anyone know of a bot that can post if there was a new CI build? What about Github Actions? https://github.com/marketplace/actions/twitter-action
That's how you do it :) https://github.com/marketplace/actions/send-tweet-action for example
I veto doing this :+1:
Back when I jokingly noted about tweets (and @12xx12 also had a note there before editing it :upside_down_face: ) the problem was/is that cuberite does not really have a notion of releases as it's mainly tracking features/versions of vanilla, not making new features on it's own.
Unless you want to spam every new commit in master to twitter then one idea would be to have everything "hot" go into some kind of devel
branch and only do devel -> master once in a while (after ""testing"" it) and push that as a tweet.
Back when I jokingly noted about tweets (and @12xx12 also had a note there before editing it :upside_down_face: ) the problem was/is that cuberite does not really have a notion of releases as it's mainly tracking features/versions of vanilla, not making new features on it's own.
Unless you want to spam every new commit in master to twitter then one idea would be to have everything "hot" go into some kind of
devel
branch and only do devel -> master once in a while (after ""testing"" it) and push that as a tweet.
so... so releases?
@bearbin Are you the only person with access to the Twitter account nowadays? Perhaps access could be granted to more people interested in tweeting about new features, if candidates exist.
Perhaps some users in the community would be interested? So far, most of the public communication has been done by different core developers, and I don't think many are that passionate about also publishing regular posts and tweets about updates.
Side note: If anyone is interested in writing news posts for the main website, feel free to create a pull request at https://github.com/cuberite/cuberite.github.io
Maybe we make the website post a tweet if there is a new news "article" availeable
@12xx12 's suggestion of posting whenever there's a new article on the website is a good idea, I'll try and keep that going if I remember.
@mathiascode I do have access to the account, not sure who else also has access if anyone, I would be happy to share the details with anyone on the team who wants to keep it up to date, but I don't want a load of junk going on it - every commit would be a partoicularly useless thing to post there.
Maybe there is a way to include a automatic tweet when generating the HTML code from the markdown code in the news article. So we don't have to manually do that.
Because everyone can open a pr we can have different people doing this and we only have to review the PR's and that's it
Sounds good?
I see the twitter account (https://twitter.com/cuberiteproject) has been inactive for quite some time (last post from 2017). I suggest the account should be closed if deemed useless, or resume maintaining it if it really has value (which isn’t the case imo...)