Author Topic: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***  (Read 365404 times)

crystalskull and 1 Guest are viewing this topic.

Offline chuckdee

  • * Destiny Supporter
  • Posts: 1308
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #50 on: Sat, 11 May 2019, 22:34:47 »
Update the git and added CI for further PR. See : https://github.com/zekth/Keebs-GB

dont use complex date formats - have people use this: https://www.unixtimestamp.com

and done ;)

Well, done until January 19, 2038.

That was my thought too, but I kept it to myself :)

Offline zekth

  • Posts: 37
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #51 on: Mon, 13 May 2019, 12:05:59 »
Update the git and added CI for further PR. See : https://github.com/zekth/Keebs-GB

dont use complex date formats - have people use this: https://www.unixtimestamp.com

and done ;)

Well, done until January 19, 2038.

That was my thought too, but I kept it to myself :)

such enthusiasm very optimistic wow thanks

Offline Sdhebert

  • Posts: 8
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #52 on: Mon, 13 May 2019, 12:28:16 »
Great idea.  The git model maps to this really well.

As for tooling to consume the data, my 2 cents would be to keep that in a separate repo.  Then it serves the purpose of a reference implementation separate from the data and management thereof.   Anyone who wants to display the data on their own site can refer to the same tooling. 

Sent from my SM-G965U using Tapatalk


Offline chuckdee

  • * Destiny Supporter
  • Posts: 1308
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #53 on: Mon, 13 May 2019, 13:01:35 »
Update the git and added CI for further PR. See : https://github.com/zekth/Keebs-GB

dont use complex date formats - have people use this: https://www.unixtimestamp.com

and done ;)

Well, done until January 19, 2038.

That was my thought too, but I kept it to myself :)

such enthusiasm very optimistic wow thanks

Well, you wanted feedback, right?

Offline zekth

  • Posts: 37
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #54 on: Mon, 13 May 2019, 14:42:26 »
Great idea.  The git model maps to this really well.

As for tooling to consume the data, my 2 cents would be to keep that in a separate repo.  Then it serves the purpose of a reference implementation separate from the data and management thereof.   Anyone who wants to display the data on their own site can refer to the same tooling. 

Sent from my SM-G965U using Tapatalk

Yes tooling will totally be in a separate repo it make sense.

@chuckdee
So you got my feedback of yours.

Offline chuckdee

  • * Destiny Supporter
  • Posts: 1308
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #55 on: Mon, 13 May 2019, 14:46:13 »
Great idea.  The git model maps to this really well.

As for tooling to consume the data, my 2 cents would be to keep that in a separate repo.  Then it serves the purpose of a reference implementation separate from the data and management thereof.   Anyone who wants to display the data on their own site can refer to the same tooling. 

Sent from my SM-G965U using Tapatalk

Yes tooling will totally be in a separate repo it make sense.

@chuckdee
So you got my feedback of yours.

Salty much?  If you're going to develop something for the community to be used universally by the community, you have to learn that it's not all going to be rah rah.  I like the idea of the unix timestamp, but seeing that it has a finite end date is a definite con that should be brought up.  Just sorry that I wasn't the one that brought it up- probably for that reason.  People ask for input, but when it's to point out a flaw many don't take it well.

Offline zekth

  • Posts: 37
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #56 on: Mon, 13 May 2019, 15:43:06 »
No salty at all, not rah rah.

The problem with unix TS is it can't be validated by a Json Schema. Adding a piece of custom code is not really in the mind of the project IMO. That's why the datetime ISO string has stayed in the model.
https://json-schema.org/understanding-json-schema/reference/string.html#format

I agree that with unix TS we would not have to handle the timezone problem. If a UI to generate the json file will be available i think we can switch to unix TS. Some people asked me in PM about it, that's why i provided the Usage section

Offline Sdhebert

  • Posts: 8
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #57 on: Sat, 18 May 2019, 20:39:03 »



I agree that with unix TS we would not have to handle the timezone problem. If a UI to generate the json file will be available i think we can switch to unix TS. Some people asked me in PM about it, that's why i provided the Usage section

Instead of a Unix timestamp that looks and feels like magic string (requiring a ui), why not just go with an ISO-8601 datetime format? Any merge could be blocked on the format not properly translating.

Sent from my SM-G965U using Tapatalk


Offline dvorcol

  • Posts: 275
  • Location: MI
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #58 on: Sat, 18 May 2019, 21:46:33 »



I agree that with unix TS we would not have to handle the timezone problem. If a UI to generate the json file will be available i think we can switch to unix TS. Some people asked me in PM about it, that's why i provided the Usage section

Instead of a Unix timestamp that looks and feels like magic string (requiring a ui), why not just go with an ISO-8601 datetime format? Any merge could be blocked on the format not properly translating.

Sent from my SM-G965U using Tapatalk

I second the ISO-8601 format.  I vote for this version:
       20190519T013758Z
       yyyymmddThhmmssZ (Z = Zulu = UTC)

Offline chuckdee

  • * Destiny Supporter
  • Posts: 1308
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #59 on: Sat, 18 May 2019, 21:54:39 »



I agree that with unix TS we would not have to handle the timezone problem. If a UI to generate the json file will be available i think we can switch to unix TS. Some people asked me in PM about it, that's why i provided the Usage section

Instead of a Unix timestamp that looks and feels like magic string (requiring a ui), why not just go with an ISO-8601 datetime format? Any merge could be blocked on the format not properly translating.

Sent from my SM-G965U using Tapatalk

I second the ISO-8601 format.  I vote for this version:
       20190519T013758Z
       yyyymmddThhmmssZ (Z = Zulu = UTC)

That had been suggested before, and what I think he arrived at a while ago.

The problem with unix TS is it can't be validated by a Json Schema. Adding a piece of custom code is not really in the mind of the project IMO. That's why the datetime ISO string has stayed in the model.
https://json-schema.org/understanding-json-schema/reference/string.html#format

I agree that with unix TS we would not have to handle the timezone problem. If a UI to generate the json file will be available i think we can switch to unix TS. Some people asked me in PM about it, that's why i provided the Usage section


Offline homerowco

  • Posts: 56
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #60 on: Tue, 21 May 2019, 13:33:05 »
> Well, done until January 19, 2038.

I think we'd be fine. I swear, if this is an issue in 2038 I will write a script to change all timestamps in the json, or I'll tell my coding AI assistant to do it :)

Offline dvorcol

  • Posts: 275
  • Location: MI
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #61 on: Tue, 21 May 2019, 13:49:27 »
> Well, done until January 19, 2038.

I think we'd be fine. I swear, if this is an issue in 2038 I will write a script to change all timestamps in the json, or I'll tell my coding AI assistant to do it :)

IBM patented the buckling spring 42 years ago.  2038 is 19 years from now.  Just saying.
« Last Edit: Tue, 21 May 2019, 13:51:02 by dvorcol »

Offline chuckdee

  • * Destiny Supporter
  • Posts: 1308
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #62 on: Tue, 21 May 2019, 19:06:29 »
> Well, done until January 19, 2038.

I think we'd be fine. I swear, if this is an issue in 2038 I will write a script to change all timestamps in the json, or I'll tell my coding AI assistant to do it :)

IBM patented the buckling spring 42 years ago.  2038 is 19 years from now.  Just saying.

I guess, more to the point, I don't see where unix timestamps give that much of an advantage over ISO that you'd build technical debt into the spec.

Offline tex_live_utility

  • Posts: 590
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #63 on: Tue, 21 May 2019, 19:21:07 »
+1 for "YYYY-MM-DD HH:mm:ss" :p

If nothing else, this should be at least somewhat accessible to non-programmer GB runners. Has any thought been given to what a hypothetical UX/UI would be like?

Offline homerowco

  • Posts: 56
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #64 on: Tue, 04 June 2019, 12:20:45 »
+1 for "YYYY-MM-DD HH:mm:ss" :p

If nothing else, this should be at least somewhat accessible to non-programmer GB runners. Has any thought been given to what a hypothetical UX/UI would be like?

so we do mysql timestamp? YYYYMMDDHHmmss on UTC?

Offline KalAl

  • Posts: 4
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #65 on: Sun, 16 June 2019, 18:18:42 »
So does this list just not get updated anymore?

Offline homerowco

  • Posts: 56
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #66 on: Fri, 21 June 2019, 10:13:30 »
So does this list just not get updated anymore?

not for a long time. too many GBs

Offline chuckdee

  • * Destiny Supporter
  • Posts: 1308
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #67 on: Fri, 21 June 2019, 17:59:01 »
There was a google sheet, but when people started getting enraged when it wasn't updated, the owner deleted it.  we can't have nice things.

Offline zekth

  • Posts: 37
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #68 on: Sat, 22 June 2019, 05:57:37 »
+1 for "YYYY-MM-DD HH:mm:ss" :p

If nothing else, this should be at least somewhat accessible to non-programmer GB runners. Has any thought been given to what a hypothetical UX/UI would be like?

so we do mysql timestamp? YYYYMMDDHHmmss on UTC?

Problem for those formats is the validation of the Json Schema. Sorry for late update i was kinda busy those times and didn't checked this out.

About the UX, i think just a form generating the proper formated json is good enought IMO. Like a single page app hosted on GH page.

NOTE: starting a POC project for this.
« Last Edit: Sat, 22 June 2019, 06:02:56 by zekth »

Offline chuckdee

  • * Destiny Supporter
  • Posts: 1308
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #69 on: Sun, 23 June 2019, 12:23:57 »
+1 for "YYYY-MM-DD HH:mm:ss" :p

If nothing else, this should be at least somewhat accessible to non-programmer GB runners. Has any thought been given to what a hypothetical UX/UI would be like?

so we do mysql timestamp? YYYYMMDDHHmmss on UTC?

Problem for those formats is the validation of the Json Schema. Sorry for late update i was kinda busy those times and didn't checked this out.

About the UX, i think just a form generating the proper formated json is good enought IMO. Like a single page app hosted on GH page.

NOTE: starting a POC project for this.

I think that the point of it is that the UX can be anything that you want it to be.  Separate the data from the presentation and let people cook up what they will with a solid foundation.

Offline zekth

  • Posts: 37
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #70 on: Sun, 23 June 2019, 18:17:05 »
Here is just a POC: https://keebdata.github.io/form/
ATM there is a lack of validations on the form, need to be updated. Also i've found some issues in the json-schema. I'll fix that soon.

the repo: https://github.com/keebdata/form
Any PR is welcome as i'm not a UX designer / developer. I prefer boring backend stuff.

Offline zekth

  • Posts: 37
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #71 on: Thu, 11 July 2019, 14:29:02 »
Anyway seems like it will not be possible atm. I'd suggest to just add the status of the GB in the name of the topic like some does but not everyone like:
  • [GB] [ON] Awesome ISO 60%
  • [GB] [OFF] Awesome ISO 60%
  • [GB] [PROD] Awesome ISO 60%
  • [GB] [SHIP] Awesome ISO 60%
  • [GB] [END] Awesome ISO 60%

Then it will be easier to find the status instead of parsing all the posts. Your thougths?

Online Signature

  • master of puppers
  • * Moderator
  • Posts: 1571
  • Less morose and more present
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #72 on: Thu, 11 July 2019, 14:33:33 »
Anyway seems like it will not be possible atm. I'd suggest to just add the status of the GB in the name of the topic like some does but not everyone like:
  • [GB] [ON] Awesome ISO 60%
  • [GB] [OFF] Awesome ISO 60%
  • [GB] [PROD] Awesome ISO 60%
  • [GB] [SHIP] Awesome ISO 60%
  • [GB] [END] Awesome ISO 60%

Then it will be easier to find the status instead of parsing all the posts. Your thougths?
That's a really good suggestion but tbh we haven't updated this in 2 years  :))

Offline zekth

  • Posts: 37
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #73 on: Thu, 11 July 2019, 14:34:52 »
Anyway seems like it will not be possible atm. I'd suggest to just add the status of the GB in the name of the topic like some does but not everyone like:
  • [GB] [ON] Awesome ISO 60%
  • [GB] [OFF] Awesome ISO 60%
  • [GB] [PROD] Awesome ISO 60%
  • [GB] [SHIP] Awesome ISO 60%
  • [GB] [END] Awesome ISO 60%

Then it will be easier to find the status instead of parsing all the posts. Your thougths?
That's a really good suggestion but tbh we haven't updated this in 2 years  :))

So update? haha I was meaning on the topic of geekhack's posts
Code: [Select]
git submodule update --recursive
« Last Edit: Thu, 11 July 2019, 14:43:37 by zekth »

Offline HoffmanMyster

  • HOFF, smol MAN OF MYSTERY
  • * Senior Moderator
  • Posts: 10534
  • Location: WI
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #74 on: Thu, 11 July 2019, 17:52:47 »
Anyway seems like it will not be possible atm. I'd suggest to just add the status of the GB in the name of the topic like some does but not everyone like:
  • [GB] [ON] Awesome ISO 60%
  • [GB] [OFF] Awesome ISO 60%
  • [GB] [PROD] Awesome ISO 60%
  • [GB] [SHIP] Awesome ISO 60%
  • [GB] [END] Awesome ISO 60%

Then it will be easier to find the status instead of parsing all the posts. Your thougths?

I think a *good* solution might be to do as you've said (specify the format so it's easy to interpret at first glance), and standardize an "Information Header" at the top of each post to list status, dates, etc. 

Then it would be great to also parse the data (that part is not too complicated, right?  I am not experienced at this, but my understanding is that it is not a crazy hurdle to overcome) and simply update this thread daily or every other day with the information. 

Am I correct in understanding that one of main troubles you've come across is setting up the website side of things?  If the data is easy to parse and gather, I'd be more than happy to update the post in this thread with the relevant data.  The main issue in the past is that the process was entirely manual and an incredible burden for whoever was going to update it.

Regardless, I support the efforts to standardize and make this easier to understand!  There are far too many GBs now to expect users to keep up to date with all of them.  :thumb:  Let me know how the mod team can support these efforts.  :)

Offline zekth

  • Posts: 37
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #75 on: Fri, 12 July 2019, 01:31:32 »
Quote
main troubles you've come across is setting up the website side of things?

Not at all, the main problem is the agreement of people using the standard and make communities contribute to it. Like i said people seems not really into this because you need to update another data source.

TBH: Once the standard is up, it's like 2 days of work to make the platform up for me. It's not a complicated project, but it needs contribution to work. It's like being a book printer without having books to print, you got the tools but not the pdf files to print.

That's why i came up with the status of the GB in the title. Why only the status? Because it doesn't require so much effort and it will be easier for everyone (me the first) to see which GB is running at the moment. It's a moderation addition but a good user feature IMO.

Offline HoffmanMyster

  • HOFF, smol MAN OF MYSTERY
  • * Senior Moderator
  • Posts: 10534
  • Location: WI
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #76 on: Fri, 12 July 2019, 08:50:39 »
Quote
main troubles you've come across is setting up the website side of things?

Not at all, the main problem is the agreement of people using the standard and make communities contribute to it. Like i said people seems not really into this because you need to update another data source.

TBH: Once the standard is up, it's like 2 days of work to make the platform up for me. It's not a complicated project, but it needs contribution to work. It's like being a book printer without having books to print, you got the tools but not the pdf files to print.

That's why i came up with the status of the GB in the title. Why only the status? Because it doesn't require so much effort and it will be easier for everyone (me the first) to see which GB is running at the moment. It's a moderation addition but a good user feature IMO.

Noted!  We'll discuss this amongst the mod team and hopefully implement something soon.  :thumb: 

Offline zekth

  • Posts: 37
Re: *** LIST OF CURRENTLY RUNNING COMMUNITY AND VENDOR GROUP BUYS ***
« Reply #77 on: Sat, 20 July 2019, 13:10:15 »
Any update? :)