Add support for proposals on `work.ubq.fi`

0x4007 commented 1 month ago

There's a lot of unaccounted for/half completed proposals and it will be best to have a dedicated view to sort and browse.

I recreated the task here because this involves work across several repositories.

The first thing that needs to be addressed is to upgrade the backend. Perhaps we can make a new repository with a better name vs devpool-directory although it isn't clear to me what the name should be yet. Perhaps we can call it "organization issue aggregator" as sort of a general purpose name. It should list every issue in our organization, and include the price tag if there is a price. If not, then no price tag should be listed
Next, on work.ubq.fi it should only filter for issues with price tags.
Then we can make a separate view that will filter for issues without price tags. It will allow us to keep the logic consolidated together.
Lastly we should figure something about syncing https://github.com/ubiquity/devpool-directory and https://github.com/ubiquity/devpool-directory-private I hope it can be rolled into this task but given that there is no details around how to implement, it might need to be broken off into a separate task.

ubiquibot[bot] commented 1 month ago

! action has an uncaught error

jordan-ae commented 1 month ago

/start

ubiquibot-dev[bot] commented 1 month ago

Warning! This task was created over 0 days ago. Please confirm that this issue specification is accurate before starting. Deadline Mon, Jul 29, 9:58 AM UTC Registered Wallet 0x2F05fD58023B0a95d1866aa0A3b672cEf05945c5

Tips:

<ul>
<li>Use <code>/wallet 0x0000...0000</code> if you want to update your registered payment wallet address.</li>
<li>Be sure to open a draft pull request as soon as possible to communicate updates on your progress.</li>
<li>Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.</li>
<ul>

ubiquibot[bot] commented 1 month ago




Deadline Mon, Jul 29, 9:58 AM UTC

Registered Wallet
0x2F05fD58023B0a95d1866aa0A3b672cEf05945c5

Tips:

Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.

ubiquibot[bot] commented 1 month ago

# No linked pull requests to close

CaptainPrinz commented 1 month ago

/start

ubiquibot-dev[bot] commented 1 month ago

Deadline Thu, Aug 15, 11:42 AM UTC Registered Wallet 0x229674f3db146E0AF0182b660F5c9232538E7e7b

Tips:

<ul>
<li>Use <code>/wallet 0x0000...0000</code> if you want to update your registered payment wallet address.</li>
<li>Be sure to open a draft pull request as soon as possible to communicate updates on your progress.</li>
<li>Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.</li>
<ul>

ubiquibot[bot] commented 1 month ago




Deadline Thu, Aug 15, 11:42 AM UTC

Registered Wallet
0x229674f3db146E0AF0182b660F5c9232538E7e7b

Tips:

Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.

CaptainPrinz commented 4 weeks ago

/stop

ubiquibot[bot] commented 4 weeks ago

+ You have been unassigned from the task

CaptainPrinz commented 3 weeks ago

@Keyrxng before taking this task again, there's some questions I want to ask. First what's the values for the environment variable in the .env file as modifying the file won't do any good if one doesnt know the values during development.

Second. In the backend, the code is complicated and one needs to study the where to actually extend the code.

I was hoping you could walk me through the file structure and all that before I start to work on nit.

Lastly in the future you may need to migrate to next.js or react and express to keep things structure as working on your current codebase is not an easy task.

Thanks . @0x4007 @jordan-ae

CaptainPrinz commented 3 weeks ago

/start

ubiquibot-dev[bot] commented 3 weeks ago

Deadline Sat, Aug 17, 8:11 PM UTC Registered Wallet 0x229674f3db146E0AF0182b660F5c9232538E7e7b

Tips:

<ul>
<li>Use <code>/wallet 0x0000...0000</code> if you want to update your registered payment wallet address.</li>
<li>Be sure to open a draft pull request as soon as possible to communicate updates on your progress.</li>
<li>Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.</li>
<ul>

ubiquibot[bot] commented 3 weeks ago




Deadline Sat, Aug 17, 8:11 PM UTC

Registered Wallet
0x229674f3db146E0AF0182b660F5c9232538E7e7b

Tips:

Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.

Keyrxng commented 3 weeks ago

@rndquu does this PR cover all aspects required for this larger task as well as the task in which it links to? - the issue timelines and PR threw me off at first, but below is correct yeah?

@CaptainPrinz after reading through this and related issues, I'm sure that you can work on refactoring the work.ubq.fi UI or the sync-solution immediately. The backend I think may be getting worked on at the moment by another contributor.

For the UI env vars, simply use the exposed key and url to login and avoid rate limiting and then make the required changes using the existing issues.

For the sync solution, I believe this is workable but I'm not sure how you'd approach it. We want to ensure that the public and private repo can easily be kept in sync at the code level, not the issues.

Lastly in the future you may need to migrate to next.js or react and express to keep things structure as working on your current codebase is not an easy task.

Appreciate this. Some projects are moving to frameworks but most will likely stay as-is

rndquu commented 3 weeks ago

So as a part of this issue we should:

Refactor https://github.com/ubiquity/devpool-directory to sync all available issues (right now it syncs only the ones with the "Price" label)
Refactor https://github.com/ubiquity/work.ubq.fi to display issues only with the "Price" label
Create a new "view" (i.e. github repository, perhaps with next.js, using css styles from https://github.com/ubiquity/work.ubq.fi) that will be able to display github issues from https://github.com/ubiquity/devpool-directory based on env variables. Possible use cases:
- show issues with the "Price" label
- show issues without the "Price" label
Lastly we should figure something about syncing https://github.com/ubiquity/devpool-directory and https://github.com/ubiquity/devpool-directory-private I hope it can be rolled into this task but given that there is no details around how to implement, it might need to be broken off into a separate task.

There's already issue for that https://github.com/ubiquity/devpool-directory-bounties/issues/25

@rndquu does this PR cover all aspects required for this larger task as well as the task in which it links to? - the issue timelines and PR threw me off at first, but below is correct yeah?

Current issue contradicts with https://github.com/ubiquity/work.ubq.fi/issues/54. If https://github.com/ubiquity/work.ubq.fi/issues/54 is not yet implemented then it may be closed as "not planned" in favor of https://github.com/ubiquity/.github/issues/115.

Keyrxng commented 3 weeks ago

If https://github.com/ubiquity/work.ubq.fi/issues/54 is not yet implemented then it may be closed as "not planned" in favor of https://github.com/ubiquity/.github/issues/115.

Refactoring devpool PR exists which is step 1 and required for step 2 I believe. If this is true then @xno-miner should be assigned to this task here and would be required to complete step 3 in order to be rewarded, is that right?

The sync issue will be treated as a separate task although the assignee should consider it if possible but is not a blocker for reward?

rndquu commented 3 weeks ago

Refactoring devpool https://github.com/ubiquity/devpool-directory/pull/1212 which is step 1.

https://github.com/ubiquity/devpool-directory/pull/1212 introduces a feature of syncing either issues with the "Price" label either without it, not both. So it was meant to be forked and run in a separate repository. While the current issue describes that https://github.com/ubiquity/devpool-directory should sync all of the github issues. That's why https://github.com/ubiquity/devpool-directory/pull/1212 contradicts with the step 1 from this comment.

and required for step 2 I believe

As far as I understand step 2 does not depend on step 1. We can refactor work.ubq.fi to display github issues with the "Price" label right now.

If this is true then @xno-miner should be assigned to this task here and would be required to complete step 3 in order to be rewarded, is that right?

Perhaps we could add https://github.com/ubiquity/work.ubq.fi/issues/54 reward to this issue and ask @xno-miner to start the current issue.

The sync issue will be treated as a separate task although the assignee should consider it if possible but is not a blocker for reward?

Yes, it could be moved to a separate task.

CaptainPrinz commented 3 weeks ago

/stop

@xno-miner can take care of it

ubiquibot[bot] commented 3 weeks ago

+ You have been unassigned from the task

xno-miner commented 3 weeks ago

/start

Refactor https://github.com/ubiquity/devpool-directory to sync all available issues (right now it syncs only the ones with the "Price" label)

Since doing it this way is going to require mostly different changes than those currently included in ubiquity/devpool-directory#1212, I'm going to close it and create a new PR. If anyone ever wanted to separate the logic again, they would just revive the old PR, because the code for it is already written.

Refactor https://github.com/ubiquity/work.ubq.fi to display issues only with the "Price" label

Create a new "view" (i.e. github repository, perhaps with next.js, using css styles from https://github.com/ubiquity/work.ubq.fi) that will be able to display github issues from https://github.com/ubiquity/devpool-directory based on env variables. Possible use cases:

show issues with the "Price" label

show issues without the "Price" label

It would be best if the new backend I will make would get quickly merged or launched in a test repo, as it would make testing the frontend easier, but if it's not possible I'll figure something out.

ubiquibot[bot] commented 3 weeks ago




Deadline Tue, Aug 20, 11:24 PM UTC

Registered Wallet
0x5ea33b5133d418f99C510ae8Bbe83f6040b99338

Tips:

Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.

Keyrxng commented 3 weeks ago

It would be best if the new backend I will make would get quickly merged or launched in a test repo, as it would make testing the frontend easier, but if it's not possible I'll figure something out.

I'm sure you should be able to test everything locally between the two codebases without ubiquity hosting or merging to development, tag me here or on tg if you need help with anything.

xno-miner commented 3 weeks ago

I have done step 1 (https://github.com/ubiquity/devpool-directory/pull/1250, xno-miner/devpool-directory/issues) and step 2 (https://github.com/ubiquity/work.ubq.fi/pull/77).

I will start doing step 3 tommorow, but I think there's no need in creating an entirely new website. The current one works fine and there will be no problem in integrating the enviromental variables into it. I will first try to do it on this one and create a new one if any problems arise.

xno-miner commented 3 weeks ago

I will start doing step 3 tommorow, but I think there's no need in creating an entirely new website. The current one works fine and there will be no problem in integrating the enviromental variables into it. I will first try to do it on this one and create a new one if any problems arise.

Done. https://github.com/ubiquity/work.ubq.fi/pull/77

ubiquity / .github