Shop OBEX P1 Docs P2 Docs Learn Events
Google Code is Closing! Move your projects to the Parallax Github! — Parallax Forums

Google Code is Closing! Move your projects to the Parallax Github!

Brett WeirBrett Weir Posts: 288
edited 2015-03-13 05:56 in Propeller 1
Now, more than ever, it's time to start moving Propeller-related projects to the Parallax Github!

Why? Because Google Code is closing down!
http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html

For those of you who don't know, we've been working to create Parallax GitHub that will be the central hub of open source development at Parallax.

You can find it here:
https://github.com/parallaxinc

Projects with a home here will soon be visible to the entire Parallax community after we launch the upcoming developer site. So don't let your project get left behind! Send email to me at contact@lamestation.com and we can go from there!

Quite a few projects have been moved over, but there are still a lot that haven't been, and even more that I don't know where they live!

Here's a list of projects completely off the top of my head that would be really awesome in the Parallax Github.
  • SimpleIDE
  • PropGCC
  • p1load
  • PropBASIC
  • Tachyon Forth
  • editor17

Feel free to suggest more; let's move these projects over!

Comments

  • ValeTValeT Posts: 308
    edited 2015-03-13 03:56
    Brett Weir wrote: »
    Projects with a home here will soon be visible to the entire Parallax community after we launch the upcoming developer site. So don't let your project get left behind! Send email to me at

    Mr. Weir,

    What is the current date for the launch of the new developer site?
  • ValeTValeT Posts: 308
    edited 2015-03-13 04:06
    Don't forget about PropWare! That needs to be added to the list.
  • Heater.Heater. Posts: 21,230
    edited 2015-03-13 05:14
    I don't see that there is a need to move everybody's projects to Parallax's repository on github.

    Clearly if Parallax has created, bought, paid for, sponsored , organized, managed or some how "owns" the project then it should probably be in their Repo.

    Reasons to do so:

    1) Having a project in the Parallax repo gives it some "seal of approval" or status.

    2) Someone want's to stop work on a useful and popular project and his happy for Parallax to take it over.

    3) Being in the Parallax repo may make your project easier to be discovered and further increase it's uptake.

    Reasons not to:

    1) Well, it's not Parallax's project. Tachyon is Peter Jakacki's. Perhaps he likes to keep it wherever he chooses. Editor17 is mindrobots'msrobots creation.

    2) Parallax does not have the manpower to be maintaining all of these things.

    Edit: Attributed the wrong robot.‎
  • mindrobotsmindrobots Posts: 6,506
    edited 2015-03-13 05:22
    Heater. wrote:
    Editor17 in mindrobots' creation.
    ‎

    CORRECTION: msrobots (Mike) did Editor17.

    I have no creations public or private. :D
  • Heater.Heater. Posts: 21,230
    edited 2015-03-13 05:35
    Oops, sorry, fixed.
  • DavidZemonDavidZemon Posts: 2,973
    edited 2015-03-13 05:56
    ValeT wrote: »
    Don't forget about PropWare! That needs to be added to the list.

    Thanks for the vote of confidence :)

    I also agree with all 5 of heater's points.

    That being said, I'd be honored if Parallax wanted PropWare in their repo.
    https://github.com/DavidZemon/PropWare
Sign In or Register to comment.