Thanks! :)

On Sat Mar 4, 2023 at 2:56 PM GMT, Umar Getagazov wrote:
> On Sat Mar 4, 2023 at 2:49 PM +03, Drew DeVault wrote:
> > I think I understand, but still, -1 for now
>
> (I think I agree with Drew. I have written a bunch of text explaining my
> opinion on this for my reply to the proposal I sent to Vlad and Renato
> (like how rich text usually suffices and the limit is not very helpful),
> but then I decided to scrap it as my explanation was a bit muddy.)

Is the idea that the user can use the Markdown-enabled long description
to create a list of projects of their own if they so desire, and that
this makes the project list superfluous?

If so, I think that makes sense — we can shelve the idea and keep it in

Thank you for the feedback!

On Fri Mar 3, 2023 at 10:59 PM GMT, Drew DeVault wrote:
> IMO 3 can come before 2, getting functionality in place is more
> important than getting pretty mock-ups since it will allow us to ship
> sooner and/or with less volunteer labor. I'll pitch in on style and
> layout as well once the time is appropriate, so don't worry too much
> about getting this part right.

ACK.

> Re: tags vs categories; I'd prefer to go with tags to match the use of
> tags on the project hub.
> ...

Nice, thank you!

Thank you for the feedback!

On Tue Feb 28, 2023 at 9:05 PM GMT, ~jman wrote:
> What is exactly blocking other kind of services being offered like
> assets for websites or videogames, composing audio tracks, flyers,
> design, pen-testing and so on? I imagine hire.sr.th a bit like "a
> craiglist for FOSS".

Thinking about it, nothing significant is blocking this. The two main
things would be (1) the wording of text on the website, and (2) the
built-in tags or categories.

> > [w.r.t.] Email as a contact
>

Thank you for your feedback!

On Tue Feb 28, 2023 at 3:49 PM GMT, Willow Barraco wrote:
> Additionnaly, I want to suggest some extra links for the
> hackers to link their donation platforms. I think this could be treated
> differently than regulars projects or website URLs. So that hire.sr.ht
> would showcase them in a better way.

Donation links could go in the normal external links list. I don't think
it makes sense to treat them in a special way. In particular, a hacker's
profile is targeted towards clients. Prospective clients might pay the
hacker for their work. Clients will not normally be interested in
donating to the hacker, or at least, this is not the purpose of
hire.sr.ht.

Reviewed-By: Renato Torres <renato@torres.id>
Reviewed-By: Umar Getagazov <umar@handlerug.me>

This is a sketch of the structure of hire.sr.ht. It is a summary of what
has been discussed so far, but also includes some new elements. All
parts are in need of revision. Ideally, this document should be
exhaustive regarding the broad features of hire.sr.ht, to help
developers decide what to work on. Please send me your comments and we
can revise it as we would a patch.

I'll briefly say how I see the immediate roadmap for hire.sr.ht:

1. Firstly, I would like to get feedback from the community on this
   proposal.

Great, thank you! :)

Signed-off-by: Vlad-Stefan Harbuz <vlad@vladh.net>
---
v1 -> v2:
* Stop ruining joke

 src/introduction/goals.md                     |  2 +-
 src/introduction/high-level-design.md         | 10 ++++----
 src/libwayland/interfaces.md                  |  2 +-
 src/libwayland/proxies.md                     |  5 ++--
 src/libwayland/util.md                        |  6 ++---
 src/protocol-design/high-level.md             |  4 +--
 src/protocol-design/interfaces-reqs-events.md | 25 ++++++++++---------
 src/protocol-design/wire-protocol.md          |  6 ++---
 src/registry.md                               | 18 ++++++-------
[message trimmed]

On Mon, 20 Feb 2023, at 19:57, c-host wrote:
> +- Helix: [hare synatx 
> highlighting](https://docs.helix-editor.com/lang-support.html)

You have a typo: “synatx”

But perhaps it is better to say something like:
“Natively supported, install through so-and-so…”