NodeMedia / NodeMediaClient-Android

20 stars 6 forks source link

[REQ] add a (GH-compliant) license file #2

Closed MarcoRavich closed 3 months ago

MarcoRavich commented 5 months ago

Hi there, 1st of all thanks for this awesome work !

Since we've 'doxed' it in our HyMPS project (under VIDEO section \ RTSP page \ Android), can you please add a GH-compliant license file for it ?

As you know, expliciting licensing terms is extremely important to let anyone better/faster understand how to reuse/adapt/modify sources (and not only) in other open projects and vice-versa.

Although it may sounds like a minor aspect, license file omission obviously causes an inconsistent generation of the relative badge too:

(badge-generator URL: https://badgen.net/github/license/NodeMedia/NodeMediaClient-Android)

You can easily set a standardized one through the GH's license wizard tool.

Last but not least, let us know how we could improve - in your opinion - our categorizations and links to resources in order to favor collaboration between developers (and therefore evolution) of listed projects.

Hope that helps/inspires !

fahimfahadleo commented 5 months ago

Screenshot from 2024-06-04 23-54-02

fahimfahadleon commented 5 months ago

can not register

On Tue, Jun 4, 2024 at 12:44 PM F.O.R.A.R.T. npo @.***> wrote:

Hi there, 1st of all thanks for this awesome work !

Since we've 'doxed' it in our HyMPS project https://forart.it/HyMPS (under VIDEO section https://github.com/forart/HyMPS#-1 \ RTSP page https://github.com/forart/HyMPS/blob/main/Video/RTSP.md#-- \ Android https://github.com/forart/HyMPS/blob/main/Video/RTSP.md#android-), can you please add a GH-compliant license file for it ?

As you know, expliciting licensing terms is extremely important to let anyone better/faster understand how to reuse/adapt/modify sources (and not only) in other open projects and vice-versa.

Although it may sounds like a minor aspect, license file omission obviously causes an inconsistent generation of the relative badge too:

https://camo.githubusercontent.com/cccd078c20bf968dbe94c8064707bd3096640017703c73dffcd2b5b42eb9f573/68747470733a2f2f62616467656e2e6e65742f6769746875622f6c6963656e73652f4e6f64654d656469612f4e6f64654d65646961436c69656e742d416e64726f6964 (badge-generator URL: https://badgen.net/github/license/NodeMedia/NodeMediaClient-Android)

You can easily set a standardized one through the GH's license wizard tool.

Last but not least, let us know how we could improve - in your opinion - our categorizations and links to resources in order to favor collaboration between developers (and therefore evolution) of listed projects.

Hope that helps/inspires !

— Reply to this email directly, view it on GitHub https://github.com/NodeMedia/NodeMediaClient-Android/issues/2, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSZWTVB5WDF2PC5FKL7JBLZFVO3JAVCNFSM6AAAAABIX3IZV6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZTENRYGU3TKMI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

fahimfahadleon commented 5 months ago

I have created a license for my project in GH and put the url of the license in the section NodePlayer node = new NodePlayer(this,URL); here. but still getting node player unauthorized toast. is there another process to do this?

On Tue, Jun 4, 2024 at 11:56 PM Fahim Fahad Leon < @.***> wrote:

can not register

On Tue, Jun 4, 2024 at 12:44 PM F.O.R.A.R.T. npo @.***> wrote:

Hi there, 1st of all thanks for this awesome work !

Since we've 'doxed' it in our HyMPS project https://forart.it/HyMPS (under VIDEO section https://github.com/forart/HyMPS#-1 \ RTSP page https://github.com/forart/HyMPS/blob/main/Video/RTSP.md#-- \ Android https://github.com/forart/HyMPS/blob/main/Video/RTSP.md#android-), can you please add a GH-compliant license file for it ?

As you know, expliciting licensing terms is extremely important to let anyone better/faster understand how to reuse/adapt/modify sources (and not only) in other open projects and vice-versa.

Although it may sounds like a minor aspect, license file omission obviously causes an inconsistent generation of the relative badge too:

https://camo.githubusercontent.com/cccd078c20bf968dbe94c8064707bd3096640017703c73dffcd2b5b42eb9f573/68747470733a2f2f62616467656e2e6e65742f6769746875622f6c6963656e73652f4e6f64654d656469612f4e6f64654d65646961436c69656e742d416e64726f6964 (badge-generator URL: https://badgen.net/github/license/NodeMedia/NodeMediaClient-Android)

You can easily set a standardized one through the GH's license wizard tool.

Last but not least, let us know how we could improve - in your opinion - our categorizations and links to resources in order to favor collaboration between developers (and therefore evolution) of listed projects.

Hope that helps/inspires !

— Reply to this email directly, view it on GitHub https://github.com/NodeMedia/NodeMediaClient-Android/issues/2, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSZWTVB5WDF2PC5FKL7JBLZFVO3JAVCNFSM6AAAAABIX3IZV6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZTENRYGU3TKMI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

MarcoRavich commented 5 months ago

is there another process to do this?

Hi there, thanks for reply.

As said, the easiest way to do so is to use the GH license wizard tool.

The other way is to manually create a LICENSE.md file in your repo.

What license have you choosed for your project ?

fahimfahadleo commented 5 months ago

Nolicense

On Wed, 5 Jun 2024, 12:00 pm F.O.R.A.R.T. npo, @.***> wrote:

is there another process to do this?

Hi there, thanks for reply.

As said, the easiest way to do so is to use the GH license wizard tool.

The other way is to manually create a LICENSE.md file in your repo.

What license have you choosed for your project ?

— Reply to this email directly, view it on GitHub https://github.com/NodeMedia/NodeMediaClient-Android/issues/2#issuecomment-2148928743, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANINOXC2C4MUWL4VWAVV7X3ZF2SRFAVCNFSM6AAAAABIX3IZV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBYHEZDQNZUGM . You are receiving this because you commented.Message ID: @.***>

MarcoRavich commented 5 months ago

@fahimfahadleo ...there are many valid alternatives to "license unknown": https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository

"Creative Commons Zero v1.0 Universal", "The Unlicense" or "Do What The F*ck You Want To Public License" - which are all recognized by GH - may fit your needs.

github-actions[bot] commented 4 months ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 3 months ago

This issue was closed because it has been inactive for 14 days since being marked as stale.