ComputerCraft is now Open Source

houseofkraft, on 02 May 2017 - 12:47 PM said:

By the way, are we allowed to fork it and create versions of our own? Because I wanted to make a custom version with new commands, notifications, enhanced BIOS, and more. Or is it still licensed?

houseofkraft, on 02 May 2017 - 08:25 PM said:

I am going to make BetterCC and its going to be really cool since it's open source

houseofkraft, on 02 May 2017 - 10:37 PM said:

Nah, BetterCC will add many features.

houseofkraft, on 03 May 2017 - 12:56 AM said:

I would love to contribute to the original repo but the BetterCC changes CC a lot. Like a GUI BIOS, and a lot more and in the rules it says it cannot have like major changes. But maybe ill make smaller changes in the original repo.

houseofkraft, on 03 May 2017 - 12:56 AM said:

I would love to contribute to the original repo but the BetterCC changes CC a lot. Like a GUI BIOS, and a lot more and in the rules it says it cannot have like major changes. But maybe ill make smaller changes in the original repo.

DannySMc, on 03 May 2017 - 09:37 AM said:

I love the idea that CC is open source, I just worry that people will make forks and new versions of it, which potentially could make lots of versions of the mod?

CrazedProgrammer, on 06 May 2017 - 01:38 AM said:

DannySMc, on 03 May 2017 - 09:37 AM said:

I love the idea that CC is open source, I just worry that people will make forks and new versions of it, which potentially could make lots of versions of the mod?

Well, this is essentially a non-issue, just like all other open-source projects.
The main repo gets the most attention and will be the best maintained version of the project, while forks and spin-offs could add functionality that doesn't belong in the main repo.
In addition to this, only the main repo will get stable official releases, so you don't have to worry about too many versions.

CLNinja, on 06 May 2017 - 01:55 AM said:

CrazedProgrammer, on 06 May 2017 - 01:38 AM said:

DannySMc, on 03 May 2017 - 09:37 AM said:

I love the idea that CC is open source, I just worry that people will make forks and new versions of it, which potentially could make lots of versions of the mod?

Well, this is essentially a non-issue, just like all other open-source projects.
The main repo gets the most attention and will be the best maintained version of the project, while forks and spin-offs could add functionality that doesn't belong in the main repo.
In addition to this, only the main repo will get stable official releases, so you don't have to worry about too many versions.

The issue i'm seeing is that if someone makes a major feature that isnt in the main repo, and wont be added for some unforeseeable reason, then that fork is going to be the most popular, and people will be more likely to use it rather than the official repo.

Weareverylucky, on 06 May 2017 - 05:08 AM said:

Yea and then making this open-source Mabey Dan can make a team that can gather up ideas of CC and make it better somewhat the community can come up with. Also the community can also help with changes and help out with tweaks. They can also be mabey a signup form for mabey helping with the CC mod team. Just my personal opinion.

Lupus590, on 06 May 2017 - 10:31 AM said:

I prefer the current method, maybe add a few people with control of the repo, but have the majority of people work via pull requests.

• There are 33 forks of ComputerCraft, possibly more. Computality is a 1.11.2 fork of CC, but isn't marked as such on GitHub.
• Of those forks, 14 of them have additional commits, many of which have been merged into the main repo.
• There have been 48 pull requests, of which 32 have been merged.
• There have been 83 new commits to the repo (I'm excluding merge commits here).
• There are 5 non-dan200 contributors.

• Added .getResponseHeaders() to HTTP responses.
• Return a HTTP response when a HTTP error occurs.
• Added a GUI to change ComputerCraft config options.
• os.time() and os.day() now accept parameters to give the real world time.
• Added os.epoch()
• Monitor text now glows in the dark.
• Added a "Pocket Computer upgrde API" so mod developers can add their own pocket upgrades.
• Added pocket.equipBack()/pocket.unequipBack() to add/remove pocket upgrades.
• shell.resolveProgram picks up on .lua files, meaning you don't need the file extension in the shell.
• The terminal pallet can now be configured with term.setPaletteColor()/term.getPaletteColor().

• Use Git: There have been several people committing via GitHub's web interface. For single file changes that's fine, but when you're changing anything more than that it gets confusing for everyone. If you don't know how to use Git, I'd really recommend following their Tutorial, or downloading one of the many GUIs out there - GitHub have a very user-friendly client.
• Don't commit to master: Create a new branch and add your commits to there. This means you can have multiple PRs on the go at once and, if master gets updated, it is much easier to rebase your commits. I've written a guide on how my repo is set up and how I handle merging.
• Think about what you're adding: Have a read through the suggestions forum and the list of closed PRs and think about what people's reactions have been to various additions. There is no point going to all the effort of a PR if it isn't going to benefit anyone. Try to avoid PRing in your favourite program or API unless you think it genuinely belongs in ComputerCraft. I'd personally prioritise improving the existing functionality of ComputerCraft than adding 20 new features.
If you're unsure, create an issue and ask. Even if your original idea is discarded, you might find some even better suggestions. There is also an IRC channel if you need to ask anything.
• Check it runs: Please, test everything. I've failed to do this once and it is dreadfully embarrassing, and causes more hassle for us all.
• Check it looks right: Have a prod through the rest of the code. Make sure yours follows roughly the same formatting and stylistic rules. While this is rather petty, a consistent codebase is easier to deal with.
• Contribute Have a look at other people's PRs. If you've got some feedback, say it (though try to be articulate).

Daniel Ratcliffe will retain the right to re-license the mod, including your contributions, in part or in whole, under other licenses.

Tag365, on 09 May 2017 - 04:30 AM said:

What does using term.setPaletteColor look like? I want to see if it is what I think it is, which is changing the rendered colors of the 16 color palette.

SquidDev, on 09 June 2017 - 09:00 PM said:

CrazedProgrammer and I have been working on improving the unofficial build server. It should be much more accessible now, as well as providing downloads for other PRs (such as CC with Cobalt and Minecraft 1.11.2 support).

You can find it at https://cc.crzd.me/.

Please remember that these are development builds - whilst they have been well tested, there may be some issues. Please report them on the ComputerCraft repository.

Builds for other PRs are served on the maven repository, so can be depended on by other mods (such as Plethora).

Bomb Bloke, on 20 June 2017 - 01:59 AM said:

More testing's always good, but actually finding the time for it is tricky… I suspect you wouldn't get all that many serious testers comparing their code across multiple builds. They'd pick one and stick with it, whereas with a single server you can force them to move up to the latest. More choice might actually be a negative.

If you did provide servers for each build, you'd at the least want to provide pre-made bases on all of them. Large enough to allow some experimentation with huge monitors, farming, mining, whatever.

Bomb Bloke, on 20 June 2017 - 10:28 AM said:

I would like for everyone to test all versions. But I believe the best option is to just offer the "latest".
Those who truly have the time and inclination to do full testing are quite capable of setting up their own servers on their local machines anyways. It's not like you need even need a second computer to do it.