UA-17470720-3

Jump to content


Photo
- - - - -

STV on GitHub


  • Please log in to reply
7 replies to this topic

#1 wizgod

wizgod

    I'm what you guys call a User

  • STV 5.0 Pro
  • PipPipPipPipPipPipPip
  • 575 posts
  • LocationThe Grid
Reputation: 149
Popular

Posted 11 April 2018 - 11:15 PM

Greetings Programs!

 

With Tarek's permission, I've put STV on GitHub - https://github.com/wizgod/STV.

 

Wg


  • ozie likes this

P.S. I love Swift... talk Swift.. Never too old school to learn yet another programming language. LOL! ;-)


#2 Dave Guerin

Dave Guerin

    Forum Master

  • STV 5.0 Pro
  • PipPipPipPipPipPipPip
  • 539 posts
  • LocationIreland
Reputation: 134
Popular

Posted 13 April 2018 - 08:01 AM

Hi wizgod,

 

Er, wow! I'm somewhat surprised that Tarek has let his "baby" out into the wild on her own! But great! Now we can fix our own STV problems :-)

 

I feel slightly uneasy with it being at https://github.com/wizgod, no offence to wizgod. A sensiblecoca GitHub handle would feel better, or just a stv handle maybe.

 

Also the LICENSE says it's under a MIT License with "Copyright © 2018 wizgod" whereas all the files say something much more restrictive with "Copyright 2011-2015 Sensible Cocoa. All rights reserved."

 

I don't want to put a dampener on proceedings but that's a couple of initial thoughts from me.

 

Open source on GitHub is the way forwards, and I certainly want to see STV go forwards, and I am willing to help wherever I'm able.

 

It would be great if Tarek himself could let us know his thoughts here as well.


Edited by Dave Guerin, 13 April 2018 - 08:07 AM.

Cheers,

Dave

www.dgapps.ie

#3 ozie

ozie

    ¯\_(ツ)_/¯

  • STV 5.0 Pro
  • PipPipPipPipPipPipPip
  • 526 posts
  • LocationAustralia
Reputation: 169
Popular

Posted 14 April 2018 - 01:58 AM

 Now we can fix our own STV problems :-)

 

 

you have the pro edition, you have the source code to do it.. you have always been able to fix any problems.. 


P.S. I hate Swift.. don't talk Swift.. Too old school to learn yet another programming language.


#4 wizgod

wizgod

    I'm what you guys call a User

  • STV 5.0 Pro
  • PipPipPipPipPipPipPip
  • 575 posts
  • LocationThe Grid
Reputation: 149
Popular

Posted 14 April 2018 - 09:04 PM

Hi wizgod,

 

Er, wow! I'm somewhat surprised that Tarek has let his "baby" out into the wild on her own! But great! Now we can fix our own STV problems :-)

 

I feel slightly uneasy with it being at https://github.com/wizgod, no offence to wizgod. A sensiblecoca GitHub handle would feel better, or just a stv handle maybe.

 

Also the LICENSE says it's under a MIT License with "Copyright © 2018 wizgod" whereas all the files say something much more restrictive with "Copyright 2011-2015 Sensible Cocoa. All rights reserved."

 

I don't want to put a dampener on proceedings but that's a couple of initial thoughts from me.

 

Open source on GitHub is the way forwards, and I certainly want to see STV go forwards, and I am willing to help wherever I'm able.

 

It would be great if Tarek himself could let us know his thoughts here as well.

 

Hey Dave,

 

It's a work in progress  :); I updated it to use the Apache License.

 

Tarek does have a sensiblecocoa account on github but he has moved on from STV onto new projects and STV is completely off his radar for any further development or to place it on github and to maintain it with his own account. Think of mine as a fork of the final official release throwing it into open source development.

 

As ozie noted, most of us already have the source code and some have already made changes ourselves but this will give the public an opportunity to use a great framework and for all of us to contribute to (and further) the development.

 

Wg


P.S. I love Swift... talk Swift.. Never too old school to learn yet another programming language. LOL! ;-)


#5 Dave Guerin

Dave Guerin

    Forum Master

  • STV 5.0 Pro
  • PipPipPipPipPipPipPip
  • 539 posts
  • LocationIreland
Reputation: 134
Popular

Posted 16 April 2018 - 07:50 AM

Hi ozie,

 

you have the pro edition, you have the source code to do it.. you have always been able to fix any problems.. 

 

I meant we (the community) can now fix our (the community) STV problems.

 

I have previously rolled my own version(s) of STV when I needed it to do/not do something the standard way.

 

 

 

Hey Dave,

 

It's a work in progress  :); I updated it to use the Apache License.

 

Tarek does have a sensiblecocoa account on github but he has moved on from STV onto new projects and STV is completely off his radar for any further development or to place it on github and to maintain it with his own account. Think of mine as a fork of the final official release throwing it into open source development.

 

As ozie noted, most of us already have the source code and some have already made changes ourselves but this will give the public an opportunity to use a great framework and for all of us to contribute to (and further) the development.

 

Wg

 

 

Hi wizgod,

 

I wasn't objecting to the MIT License, just highlighting the marked difference between any open source license and the license in all the files. MIT seems to be the default license for open source projects on GitHub, it's certainly less wordy than the Apache license. I'm not sure, but with the addition of the original "LICENSE AGREEMENT (Original SensibleCocoa).rtf" file to the repository doesn't that make it all closed source now?? Is a release from Tarek required to re-license all his code as MIT or Apache? 

 

 

I would really like STV to continue, and if STV is now totally off Tareks radar then the only way it is going to continue is from the community, which is probably just you, ozie, and me currently :-)

 

Making the STV code Open Source is the way forward then, but needs to be done correctly to avoid problems down the line.

 

If Tarek/Sensible Cocoa as the current copyright holder made the original commit to GitHub with the MIT/Apache license for all the files, maybe with everything under a more generic/community SensibleTableView GitHub user then I wouldn't feel as uneasy with it as I am currently.

 

STV certainly has a few issues with iOS11, which I now need to investigate myself, and I'd certainly want to contribute any fixes back to a community SensibleTableView/STV.

 

 

 

Just my 2c worth :-)


Cheers,

Dave

www.dgapps.ie

#6 Dave Guerin

Dave Guerin

    Forum Master

  • STV 5.0 Pro
  • PipPipPipPipPipPipPip
  • 539 posts
  • LocationIreland
Reputation: 134
Popular

Posted 16 April 2018 - 08:48 AM

The sort of thing I'm talking about is similar to the closed source Parse becoming open source on GitHub as parse-community/parse-server with this license:

 

https://github.com/p.../master/LICENSE


Cheers,

Dave

www.dgapps.ie

#7 wizgod

wizgod

    I'm what you guys call a User

  • STV 5.0 Pro
  • PipPipPipPipPipPipPip
  • 575 posts
  • LocationThe Grid
Reputation: 149
Popular

Posted 17 April 2018 - 11:04 PM

Hi Dave,

 

I talked to Tarek and he suggested returning to the MIT license which he considers to be one of the most flexible ones.

 

As far as the repo, he's fine where it's at for now and if it starts to have a fair amount of activity, we'd look at creating a dedicated account at that time.

 

He recommended adding you (and ozie's in the list too  ;) ) to the list of contributors if you want.

 

Wg


P.S. I love Swift... talk Swift.. Never too old school to learn yet another programming language. LOL! ;-)


#8 Dave Guerin

Dave Guerin

    Forum Master

  • STV 5.0 Pro
  • PipPipPipPipPipPipPip
  • 539 posts
  • LocationIreland
Reputation: 134
Popular

Posted 18 April 2018 - 01:49 AM

Hi wizgod,

 

I'd agree with Tarek on the MIT license being the most flexible, and also one of the least wordy. There should be an addition at the bottom saying it was open sourced with Tarek's permission on 12 April 2018. And all the headers should have their copyright changed to also reflect that, maybe only as files are edited. And the "LICENSE AGREEMENT (Original SensibleCocoa).rtf" file should be removed. As it stands currently, anyone who actually reads the license(s) would not be able to actually use any of the code.

 

If Tarek is happy with where it is for now, then I'm happy :-)

 

And I'd be honoured to be a contributor, although I'm not that familiar with GitHub so I'm not quite sure how that  all works.

 

 

STV has issues with iOS 11 that I was looking at all yesterday but without any fix. Are we going to continue discussion of STV here, or take it to GitHub?

 

And just to note, the commit of 3 days ago that moved the source code to it's own folder broke the ability to include the framework as source code in a project, Xcode can't seem to find any of the files to edit, but can still build the framework somehow.

 

 

Looking forward to contributing and moving STV forward!


Cheers,

Dave

www.dgapps.ie




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users